Fix contradictory model method naming conventions in example#76
Open
d57montes wants to merge 1 commit into
Open
Fix contradictory model method naming conventions in example#76d57montes wants to merge 1 commit into
d57montes wants to merge 1 commit into
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
In
python.md,Model method naming conventionsstates"For query methods (ie methods that look something up and return it), prefix with get_.
For setter methods (ie methods that set fields and call save), prefix with set_."
However, an example in
Group methods and properties on modelsdoes not use these conventions. This edit corrects the example.