Skip to content
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.

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

Add: Eslint rule camelCase #4062

Merged
merged 2 commits into from
Jun 14, 2024
Merged

Conversation

daniele-mng
Copy link
Contributor

@daniele-mng daniele-mng commented Jun 12, 2024

What

Add eslint rule for camelCase variables.

Why

Currently, there are over 5000 instances of non-camelCase variable names in our codebase. This not only goes against JavaScript conventions but also makes our code less readable and harder to maintain. By enforcing camelCase naming, we can gradually rectify this issue and prevent it from happening in the future.

References

Checklist

  • Tests

@daniele-mng daniele-mng marked this pull request as ready for review June 12, 2024 15:02
@daniele-mng daniele-mng requested a review from a team as a code owner June 12, 2024 15:02
Copy link

github-actions bot commented Jun 12, 2024

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Snapshot Warnings

⚠️: No snapshots were found for the head SHA fe67b9a.
Ensure that dependencies are being submitted on PR branches and consider enabling retry-on-snapshot-warnings. See the documentation for more information and troubleshooting advice.

OpenSSF Scorecard

PackageVersionScoreDetails

Scanned Manifest Files

Copy link

Conventional Commits Report

Type Number
Added 1

🚀 Conventional commits found.

Copy link
Contributor

@bjoernricks bjoernricks left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Merging this PR will create a ton of warnings

@bjoernricks
Copy link
Contributor

Merging this PR will create a ton of warnings

It even results in failing linting at the CI because we treat warnings as errors. Should we allow warnings for now?

Copy link

codecov bot commented Jun 14, 2024

Codecov Report

Attention: Patch coverage is 0% with 688 lines in your changes missing coverage. Please review.

Project coverage is 72.25%. Comparing base (5a78a99) to head (e148f55).
Report is 1 commits behind head on main.

Current head e148f55 differs from pull request most recent head fe67b9a

Please upload reports for the commit fe67b9a to get more accurate results.

Files Patch % Lines
allowedSnakeCase.cjs 0.00% 687 Missing and 1 partial ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4062      +/-   ##
==========================================
- Coverage   72.65%   72.25%   -0.40%     
==========================================
  Files        1062     1064       +2     
  Lines      120912   121658     +746     
  Branches     5990     6002      +12     
==========================================
+ Hits        87843    87899      +56     
- Misses      33040    33728     +688     
- Partials       29       31       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Contributor

@bjoernricks bjoernricks left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice! 👍🏻

@bjoernricks bjoernricks enabled auto-merge (rebase) June 14, 2024 07:59
@bjoernricks bjoernricks force-pushed the Add-eslint-rule-camelCase-variables branch from e148f55 to fe67b9a Compare June 14, 2024 07:59
@bjoernricks bjoernricks merged commit 12f9e5c into main Jun 14, 2024
11 checks passed
@bjoernricks bjoernricks deleted the Add-eslint-rule-camelCase-variables branch June 14, 2024 08:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants