fix: Add Ajv type coercion for Express 5 query parameter compatibility #1388
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.
Description
This PR addresses query parameter type handling changes introduced by Express 5. (see #1340)
Express 5 introduced a breaking change where req.query is now a read-only getter instead of a writable property. This means that custom middleware can no longer reassign
req.queryto convert types, causing schema validation to fail when expecting any type but a string.The solution uses Ajv's built-in
coerceTypesfeature to handle type conversion during schema validation.Changes made
1 - Enabled Ajv type coercion: allows for automatic type conversion of query string values;
2 - Removed custom querystring middleware and its tests: no longer needed since Ajv handles type coercion;