New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Consider refactor for known annotated metadata application in recursive cases #9281

Open

sydney-runkle opened this issue Apr 18, 2024 · 1 comment

Milestone

Member

sydney-runkle commented Apr 18, 2024

See #9279 for a start.

Consider other schemas like chain, json or python, etc.

Member Author

sydney-runkle commented Apr 18, 2024

Also, as suggested by @dmontagu:

ArgumentsSchema, CallSchema, CustomErrorSchema, JsonSchema, DefinitionsSchema, DefinitionReferenceSchema, I think these would all have the same issues
CustomErrorSchema and JsonSchema seem like real potential issues
The Definition and maybe DefinitionReference ones also seem like real potential issues with things like type aliases

sydney-runkle added this to the v2.8.0 milestone

sydney-runkle mentioned this issue

Fix strict application to function-after with use_enum_values #9279

Merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment