From b1e9bb0c604c05362d5e26532e6dcd3c28436758 Mon Sep 17 00:00:00 2001 From: Andrew Rosiclair Date: Tue, 20 Oct 2026 11:11:28 -0400 Subject: [PATCH 1/3] Clarify boolean naming convention Fixes the current wording to expand what's allowed as a prefix for a bool --- general.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/general.md b/general.md index 498ff37..64834de 100644 --- a/general.md +++ b/general.md @@ -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`). - Count variables should be suffixed with "count" (e.g., `transactionsCount` instead of `numberTransactions`). ## Acronyms From a252f293f095ed22df512298c4aca1290ecefaaf Mon Sep 17 00:00:00 2001 From: Andrew Rosiclair Date: Tue, 20 Oct 2026 11:18:43 -0400 Subject: [PATCH 2/3] another example --- general.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/general.md b/general.md index 64834de..1390743 100644 --- a/general.md +++ b/general.md @@ -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 an auxillary verb such as "is", "should", "has", "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 From 020a7dc236a5f04b7e4e26a784063bd857458227 Mon Sep 17 00:00:00 2001 From: Andrew Rosiclair Date: Tue, 20 Oct 2026 11:21:19 -0400 Subject: [PATCH 3/3] typo --- general.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/general.md b/general.md index 1390743..1ce487a 100644 --- a/general.md +++ b/general.md @@ -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 an auxillary verb such as "is", "should", "has", "does", or "will" (e.g., `shouldRunThis`, `doesHaveTransactions`, "didFail"). +- 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