Add CI Rule for Testing camelCase Naming Convention
Open
developer-experience
- Dominant language
- JavaScript
- Stars
- 27.2k
- Forks
- 5.6k
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 46
Description
Develop a CI rule to verify that all identifiers in the codebase that are not dictated by upstream adhere to the camelCase naming convention.
Contributor guide
Research direction
Start by locating the repository's CI configuration and the existing identifier or linting checks. Define how upstream-dictated identifiers are identified and which code paths are covered, then verify that CI fails for non-camelCase identifiers and passes for allowed upstream names.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100