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

[v5] Configure stricter eslint rules and auto fixers #11274

Open
raix opened this issue Aug 3, 2021 · 0 comments
Open

[v5] Configure stricter eslint rules and auto fixers #11274

raix opened this issue Aug 3, 2021 · 0 comments

Comments

@raix
Copy link
Contributor

raix commented Aug 3, 2021

Is your proposal related to a problem?

Now days there are eslint rules out there helping developers move to modern api's and write better code - some with autofixers.

This issue was sparked by input from this comment good input - but also requires CRA to have more oppinions on things like best practice and good code conventions. (so potentially a discussion for a smaller forum as it will be oppinionated discussions - exercise will be to try to stay objectively on the pros/cons on different code styles eg. to prevent "footguns"/improve readability/improve git diffs etc....)

Describe the solution you'd like

The CRA project will have to figure out if we want to move towards being more oppinionated / strict about these things.

Describe alternatives you've considered

Additional context

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant