Fix typo in docs for new private dunder pydantic method names #7657
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
please review |
hramezani
approved these changes
Sep 27, 2023
|
Thanks @austinorr |
|
I'm not sure this is really correct - we have |
Ah, you are right. just created a revert PR #7662 Sorry for that! |
hramezani
added a commit
that referenced
this pull request
Sep 27, 2023
My mistake all, thanks for the quick responses and very sorry for the extra noise. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Change Summary
Relatively trivial docs change to indicate new naming convention for dunder methods. Current docs don't match the methods listed in the table since the regex in the narrative includes more wildcards than the actually used convention.
Selected Reviewer: @davidhewitt