Fix msgspec pattern and optional annotated type #1606
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.
Fixes #1605.
Also fixes an issue with the ordering/nesting of the Optional and Annotated types that I discovered while testing the
Meta(pattern='...')
constraint.msgspec.Meta
withpattern
argument can only apply to astr
type not aOptional[str]
type as was previously being generated. So it's necessary to override the type hint behaviour when a field is Optional and annotated with amsgspec.Meta
constraint.