Skip to content

Clarify boolean naming convention #25

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.

Sign up for GitHub

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

Merged
amyevans merged 3 commits into from
Oct 20, 2026
Merged

Clarify boolean naming convention #25

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b1e9bb0
Clarify boolean naming convention
arosiclair Oct 20, 2026
a252f29
another example
arosiclair Oct 20, 2026
020a7dc
typo
arosiclair Oct 20, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion general.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ Language Agnostic Coding Standard
## Variables
- Variables should always start lowercase and be camelCase (caveat see #Acryonyms)
- Use of full words within names is RECOMMENDED; avoid abbreviations that create ambiguity (e.g. Bad: msg Good: message)
- Boolean variables should be prefixed with "should", "does", or "will" (e.g., `shouldRunThis`, `doesHaveTransactions`).
- Boolean variables should be prefixed with an auxillary verb such as "is", "should", "has", "does", or "will" (e.g., `shouldRunThis`, `doesHaveTransactions`, `didFail`).
- Count variables should be suffixed with "count" (e.g., `transactionsCount` instead of `numberTransactions`).

## Acronyms
Expand Down