You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update ESLint naming conventions and configuration
- Revised the archive file to reflect recent updates in ESLint naming conventions, including the transition to PascalCase for boolean variables and functions, and the addition of new function prefixes such as 'setup', 'create', 'init', and 'build'.
- Enhanced `eslint.config.mjs` to implement these changes, ensuring better support for naming patterns and improved variable filtering.
- Introduced a new rule for true constants to use UPPER_CASE formatting, further refining the naming standards.
These updates enhance code quality and consistency across the TypeScript codebase, promoting maintainability and clarity.
Implement comprehensive ESLint naming convention rules based on [naming-cheatsheet](https://github.com/kettanaito/naming-cheatsheet) principles to improve code quality and consistency across the TypeScript codebase.
12
12
13
-
### Recent Enhancements (2025-08-11)
13
+
### Recent Enhancements (2025-01-15)
14
+
-**Fixed EnumMember Format**: Corrected typo in enumMember format rule from 'Pascaнадо ли lCase' to 'PascalCase'
15
+
-**Enhanced Boolean Variable Rules**: Changed to PascalCase formatting for boolean variables to support patterns like `isValid`, `hasPermission`
16
+
-**Enhanced Function Naming Rules**: Changed to PascalCase formatting for functions to support patterns like `createRepoInstance`, `setupRedminePoolMock`
17
+
-**Expanded Function Prefixes**: Added 'setup', 'create', 'init', 'build' prefixes for comprehensive coverage
18
+
-**Fixed Variable Filtering**: Improved variable naming rules to prevent false positives on regular variables
19
+
20
+
### Previous Enhancements (2025-08-11)
14
21
-**Enhanced Boolean Variable Rules**: Enforced camelCase formatting for boolean variables while maintaining prefix requirements
15
22
-**Enhanced Function Naming Rules**: Enforced camelCase formatting for functions while maintaining comprehensive prefix requirements
16
23
-**Improved Validation**: Functions and boolean variables now reject invalid patterns like `get_user` or `IS_VALID`
@@ -23,14 +30,14 @@ Implement comprehensive ESLint naming convention rules based on [naming-cheatshe
23
30
5. Follow naming-cheatsheet principles
24
31
6. Add support for enum members (PascalCase/UPPER_CASE)
25
32
7. Handle object literal properties with string literals
0 commit comments