Repository navigation
Discuss and implement variable naming criteria #2342
Description
Terms
- I have searched open and closed issues
- I agree to follow activist's Code of Conduct
Issue
Something that has been discussed multiple times in activist dev syncs is that there are some projects that have specific naming criteria based on the type of the variable - i.e. all booleans must be is*.
This issue would discuss what other rules would be that we want to apply. Specifically we would always use the same rules for the backend and frontend and only change the case.
Metadata
Metadata
Assignees
Type
Projects
- Status
Activity
MayurK-cmd commentedon Sep 2, 2026
Hey Can i work on this?
andrewtavis commentedon Sep 2, 2026
You'd be welcome to look into this, @MayurK-cmd, but maybe you could write out an explanation in the issue about what you'd suggest for the naming conventions and what your sources are?
MayurK-cmd commentedon Sep 3, 2026
i would audit current naming patterns in both codebases, define clear rules (booleans with
is*/has*prefixes, collections always plural, etc.), document inSTYLEGUIDE.md, then add ESLint and pylint rules to enforce them. I'll also update.pre-commit-config.yamlto catch violations early. Happy to start with the audit phase and share findings.andrewtavis commentedon Sep 3, 2026
Feel free to start with the audit phase, and please do reference industry best practices for this :)
MayurK-cmd commentedon Sep 3, 2026
on it