-
Notifications
You must be signed in to change notification settings - Fork 412
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.
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
docs(parser): improve documentation with Pydantic best practices #5925
Conversation
Thanks a lot for your first contribution! Please check out our contributing guidelines and don't hesitate to ask whatever you need. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @AlphaWong! Thanks a lot for suggesting this change, I think this make lot of sense!
I just left a small comment to improve the message. Please let me know when you change this and then we can merge this PR.
Co-authored-by: Leandro Damascena <lcdama@amazon.pt> Signed-off-by: Alpha <AlphaWong@users.noreply.github.com>
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved! Thanks @AlphaWong!
Awesome work, congrats on your first merged pull request and thank you for helping improve everyone's experience! |
Issue number: #5926
Summary
root_validator
(deprecated as of version 3.0.0) but the doc is outdated, theroot_validator
doc still appears on 3.2.0.Changes
If customers are migrating their library from version 2, refer to the latest documentation for updated methods compatible with
root_validator
User experience
N/A
Checklist
If your change doesn't seem to apply, please leave them unchecked.
Is this a breaking change?
nopeRFC issue number:
Checklist:
Acknowledgment
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.