Skip to content

Commit

Permalink
Fix urls
Browse files Browse the repository at this point in the history
  • Loading branch information
255kb committed Dec 9, 2024
1 parent 10ecfc8 commit c848ddb
Show file tree
Hide file tree
Showing 4 changed files with 7 additions and 8 deletions.
2 changes: 1 addition & 1 deletion content/docs/v9.0.0/api-endpoints/routing.md
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,7 @@ You can also retrieve the route parameters by using the `{{urlParam 'paramName'}

Routes **must** be declared without query parameters as they are not part of the route path. They can only be added to the request when calling an endpoint.

Query parameters can be retrieved with the **[`queryParam`](docs:/docs/latest/templating/mockoon-request-helpers/#queryparam) and [`queryParamRaw`](docs:/docs/latest/templating/mockoon-request-helpers/#queryparamraw) helpers** and are available in the **[response rules](docs:route-responses/dynamic-rules)** to check their content and serve different responses based on them.
Query parameters can be retrieved with the **[`queryParam`](docs:templating/mockoon-request-helpers/#queryparam) and [`queryParamRaw`](docs:templating/mockoon-request-helpers/#queryparamraw) helpers** and are available in the **[response rules](docs:route-responses/dynamic-rules)** to check their content and serve different responses based on them.

**Arrays and objects are supported** in the query string. For more information, please refer to the [query parameters documentation](docs:requests/query-parameters).

Expand Down
2 changes: 1 addition & 1 deletion content/docs/v9.0.0/requests/query-parameters.md
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ Parsed query parameters:

## Where can I access the query parameters?

The parsed query parameters will be available **everywhere [templating helpers](docs:templating/overview) are supported**: response body, headers, rules, data buckets, callbacks, etc. You will be able to use the [`queryParam`](docs:templating/mockoon-request-helpers#queryparam) and [`queryParamRaw`](docs:/docs/latest/templating/mockoon-request-helpers/#queryparamraw) to access the parsed parameters and create dynamic responses based on it.
The parsed query parameters will be available **everywhere [templating helpers](docs:templating/overview) are supported**: response body, headers, rules, data buckets, callbacks, etc. You will be able to use the [`queryParam`](docs:templating/mockoon-request-helpers#queryparam) and [`queryParamRaw`](docs:templating/mockoon-request-helpers/#queryparamraw) to access the parsed parameters and create dynamic responses based on it.

The parameters will also be **available in the [response rules](docs:route-responses/dynamic-rules)** to check their content and serve different responses based on them.

Expand Down
2 changes: 1 addition & 1 deletion content/docs/v9.0.0/requests/supported-body-formats.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ Invalid bodies will be parsed as strings.

## What can I do with the parsed body?

The parsed body will be available **everywhere [templating helpers](docs:templating/overview) are supported**: response body, headers, rules, data buckets, callbacks, etc. You will be able to use helpers like [`body`](docs:/docs/latest/templating/mockoon-request-helpers/#body) and [`bodyRaw`](docs:/docs/latest/templating/mockoon-request-helpers/#bodyraw) to access the parsed body content and create dynamic responses based on it.
The parsed body will be available **everywhere [templating helpers](docs:templating/overview) are supported**: response body, headers, rules, data buckets, callbacks, etc. You will be able to use helpers like [`body`](docs:templating/mockoon-request-helpers/#body) and [`bodyRaw`](docs:templating/mockoon-request-helpers/#bodyraw) to access the parsed body content and create dynamic responses based on it.

The body will also be **available in the [response rules](docs:route-responses/dynamic-rules)** to check its content and serve different responses based on it.

Expand Down
9 changes: 4 additions & 5 deletions pages/releases/[version].tsx
Original file line number Diff line number Diff line change
Expand Up @@ -37,8 +37,9 @@ export async function getStaticProps({
const files = require.context('../../content/releases/', true, /\.\/.+\.md$/);
const releasePaths = files.keys().sort(sortPathBySemver);

const fileContent =
await require(`../../content/releases/${params.version}.md`);
const fileContent = await require(
`../../content/releases/${params.version}.md`
);
const release = matter(fileContent.default);

let releases = releasePaths.map((releasePath, releasePathIndex) => {
Expand Down Expand Up @@ -84,9 +85,7 @@ export default function Release(props: {
<div className='col-12 col-lg-4 mb-8 pe-lg-8'>
<aside className='flex-grow-1 sticky-top pt-4'>
<ul className='card-list list mb-6'>
<h6 className='fw-bold text-uppercase mb-2'>
Applications releases
</h6>
<h6 className='fw-bold text-uppercase mb-2'>Versions</h6>
{props.releases.map((release, releaseIndex) => {
return (
<li
Expand Down

0 comments on commit c848ddb

Please sign in to comment.