fix: allow limited use of type annotations #6322
Merged
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
Allows Pattern, Min, and Max to be specified on List or Map component types. This initial version looks specifically for List and Map types - this may be too restrictive, but it keeps the logic simplier. If there is a method as the annotatedmember, it will use the same simple logic as the validation rules to find the field.
I also commented out getting the minLength / maxLength from the string schema for the min / max - that is currently not used and it's not correct as minLength / maxLength are distinct and set specfically for strings.
cc @adriansuarez
closes: #6282
Type of change
test, version modification, documentation, etc.)
Checklist