fix(event-handler): preserve metadata constraints in parameter validation #7609
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.



Issue number: closes #7600
Fixes a regression introduced in PR #7227 where
annotated_typesconstraints (likeInterval) were not being validated in request parameters.The issue occurred in the
copy_field_info()function when switching fromFieldInfo.from_annotation()tocopy(). While this preserved discriminator functionality, it discarded constraint metadata from nestedAnnotatedtypes.Changes
copy_field_info()to recursively extract and preserve constraint metadata while filtering outFieldInfoinstancesget_field_info_annotated_type()to maintain consistencyBodyandQueryparametersUser experience
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.