-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Improve docstrings for SON parameters #919
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
Conversation
Line 1446 of this file originally read as follows: > "`filter` (optional): a SON object specifying elements..." I believe "SON" is a typo for "JSON", so have updated it to read as follows: > "`filter` (optional): a JSON object specifying elements..."
Haha! I did write this PR in fear that I would display my ignorance - a well-founded fear, it seems :P There may be merit in disambiguating for newbies like me by linking to the Its something I'm happy to do if you feel it would add value, but I'm also comfortable if you close this issue. Thanks! |
Sounds good! It would be:
|
Per advice in PR discussion - I searched for all instances of " SON", checked to make sure they were part of documentation and not code, and replaced with `:class:`~bson.son.SON``
(and learned about the power of "Preview changes" in the process!)
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.
Thank you!
Test failure is being tracked in https://jira.mongodb.org/browse/PYTHON-3188 |
Thanks for the opportunity to contribute! (I presume test failures aren't for me to worry about, given that they predate this PR?) |
That's right, we're already working on that one separately. |
Line 1446 of this file originally read as follows:
I believe "SON" is a typo for "JSON", so have updated it to read as follows: