Skip to content
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

Terminology of formatting conventions #191

Open
joeri-hu opened this issue Feb 24, 2022 · 1 comment
Open

Terminology of formatting conventions #191

joeri-hu opened this issue Feb 24, 2022 · 1 comment
Assignees
Labels
content needs improvement Module 5 Questions/Problems with: Odds and Ends

Comments

@joeri-hu
Copy link

Referring to Module 5: Odds and Ends under the section Naming Conventions, there is a lot of emphasis put on the distinction between different formatting conventions for class names. It states that CamelCase should be used and then goes on to show the differences with the example of ShoppingList and shoppingList, implying that the latter is not CamelCase.

In this scenario, the term CamelCase is a poor choice since both styles qualify as CamelCase. Personally, I've always used the terms camelCase and PascalCase to make the distinction. The PEP8 style-guide seems to use the term mixedCase to refer to the former.

In any case, I feel that using the term CamelCase to solely refer to CapWords (and not mixedCase) is definately not the way to go and will only lead to more confusion to the reader.

@rsokl rsokl added content needs improvement Module 5 Questions/Problems with: Odds and Ends labels Feb 25, 2022
@rsokl
Copy link
Owner

rsokl commented Feb 25, 2022

Thanks for bringing this to my attention. It does look like camelCase and CamelCase are both valid. I'll update this section to use the term CapWords instead,

@rsokl rsokl self-assigned this Feb 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content needs improvement Module 5 Questions/Problems with: Odds and Ends
Projects
None yet
Development

No branches or pull requests

2 participants