fix(docs, fastify-example): add example for an endpoint with multi query param #133
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Checklist
npm test
locally and all tests are passing.Context
This is a PR whose goal is to fix issues #134 and #135. While this issues were open we were not sure if they were bugs or not.
After a bit of investigation there is no bug related to them but we have detected that documentation is sparse on this topic (Which is normal because it is a very edge case).
Thus we have added small changes that do not change the behaviour of bauta.js but we have added a bit of documentation whose goal is to reduce the timing invested in troubleshooting possible issues with schema request validations.
Summary
bautajs-core
bautajs-fastify
bautajs-fastify-example
We have added an endpoint that illustrates how to proceed if you need to have a GET with query params as array using the default method (using multi and indicating the field name for each value).
We have added an endpoint similar to the previous one but that uses a query param as array using csv (comma separated values).--> Removed to avoid using directlyqs
library as dependency in bauta.js project.Documentation
validation.md
that details a bit more about request validation and request parsing.