-
Notifications
You must be signed in to change notification settings - Fork 299
Use consistent naming for Django REST framework #977
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
Codecov Report
@@ Coverage Diff @@ ## master #977 +/- ## ======================================= Coverage 96.82% 96.82% ======================================= Files 65 65 Lines 3904 3904 ======================================= Hits 3780 3780 Misses 124 124
Continue to review full report at Codecov.
|
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.
hmmm, I'd argue that DRF gets it wrong and the F should be Title case....
Uh oh!
There was an error while loading. Please reload this page.
Description of the Change
This follows the naming DRF uses in its own documentation with an uppercase
REST
and all lowercaseframework
.Checklist
CHANGELOG.md
updated (only for user relevant changes)AUTHORS