-
-
Notifications
You must be signed in to change notification settings - Fork 1
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
Make ESLint config stricter #22
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #22 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 1 1
Lines 6 6
Branches 1 1
=========================================
Hits 6 6
Continue to review full report in Codecov by Sentry.
|
e133272
to
9e48c48
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the additional configurations and improvements @arkadiuszbachorski!
The comments were really helpful, the configuration sounds reasonable to me and I trust your expertise and experience in the benefits of the different rules.
Co-authored-by: Paul Schmiedmayer <PSchmiedmayer@users.noreply.github.com>
Make ESLint config stricter
♻️ Current situation & Problem
Current ESLint config is fine, but it can be configured way strictier. It enforces good practives, improves quality of the code and guarantees consistency.
⚙️ Release Notes
Code of Conduct & Contributing Guidelines
By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines: