From d5f999097d82e7c6d0d422a1595632b4aa8543d4 Mon Sep 17 00:00:00 2001 From: Guillaume Date: Mon, 18 Nov 2024 09:22:18 +0100 Subject: [PATCH] Fix links --- content/docs/latest/api-endpoints/routing.md | 2 +- content/docs/latest/requests/query-parameters.md | 2 +- content/docs/latest/requests/supported-body-formats.md | 2 +- content/tutorials/self-host-mock-api-server-cli.md | 4 ++-- 4 files changed, 5 insertions(+), 5 deletions(-) diff --git a/content/docs/latest/api-endpoints/routing.md b/content/docs/latest/api-endpoints/routing.md index f30667ac..8f51203d 100644 --- a/content/docs/latest/api-endpoints/routing.md +++ b/content/docs/latest/api-endpoints/routing.md @@ -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). diff --git a/content/docs/latest/requests/query-parameters.md b/content/docs/latest/requests/query-parameters.md index d831456b..520b0b1d 100644 --- a/content/docs/latest/requests/query-parameters.md +++ b/content/docs/latest/requests/query-parameters.md @@ -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. diff --git a/content/docs/latest/requests/supported-body-formats.md b/content/docs/latest/requests/supported-body-formats.md index 4594d06b..80cffff6 100644 --- a/content/docs/latest/requests/supported-body-formats.md +++ b/content/docs/latest/requests/supported-body-formats.md @@ -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. diff --git a/content/tutorials/self-host-mock-api-server-cli.md b/content/tutorials/self-host-mock-api-server-cli.md index 6e5acc8f..7b24be6a 100644 --- a/content/tutorials/self-host-mock-api-server-cli.md +++ b/content/tutorials/self-host-mock-api-server-cli.md @@ -77,7 +77,7 @@ Another option is to directly pass an **OpenAPI specification file**. It's parti As above, you can provide a path to a local OpenAPI specification file or directly the file's URL. -> ⚠️ There is currently no equivalent between some of the Mockoon's features and the OpenAPI specifications ([more info](docs:openapi/openapi-specification-compatibility)). If you want to run your mock API created in Mockoon in the CLI with all its features (rules, etc.), you must use Mockoon's data file ([see above](#provide-a-mockoons-environment-file)) and not the [OpenAPI export feature](/docs/latest/openapi/import-export-openapi-format/). +> ⚠️ There is currently no equivalent between some of the Mockoon's features and the OpenAPI specifications ([more info](/docs/latest/openapi/openapi-specification-compatibility/)). If you want to run your mock API created in Mockoon in the CLI with all its features (rules, etc.), you must use Mockoon's data file ([see above](#provide-a-mockoons-environment-file)) and not the [OpenAPI export feature](/docs/latest/openapi/import-export-openapi-format/). ### Step 4. Start you mock API @@ -130,7 +130,7 @@ This file contains all the log entries (all levels) produced by the running mock > 💡 File logging is disabled where running Mockoon CLI using our Docker image. You can also disable it with the `--disable-log-to-file` flag. -In addition, the **logs can be available through the [Admin API](docs/latest/admin-api/transaction-logs/)**, which is enabled by default and exposed in each running mock on the `/mockoon-admin` path. You can make a GET request to `http://localhost:3000/mockoon-admin/logs` to retrieve the logs. The information available through the Admin API is the same as the one available in the Desktop application's "Logs" tab. +In addition, the **logs can be available through the [Admin API](/docs/latest/admin-api/transaction-logs/)**, which is enabled by default and exposed in each running mock on the `/mockoon-admin` path. You can make a GET request to `http://localhost:3000/mockoon-admin/logs` to retrieve the logs. The information available through the Admin API is the same as the one available in the Desktop application's "Logs" tab. ### Step 6. Deploy Mockoon CLI using Docker