feat: improve "key" property in validation error messages #4216
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
Start "key" with an array index when the validation error applies to a request body or a query parameter that is a list.
Use alternative name for query parameters, cookies, and headers in "key" instead of the parameter's name in a route handler's signature.
Parameters in route handlers that are not the request body but whose names start with "data" will not have their validation error message "source" set to "body".
Use a "key" that better resembles the format that msgspec uses when an ExtendedMsgSpecValidationError is raised.
Closes
Closes #4215