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

--strict mode #35

Open
saadq opened this issue Feb 6, 2019 · 1 comment
Open

--strict mode #35

saadq opened this issue Feb 6, 2019 · 1 comment
Labels
enhancement New feature or request. feedback wanted This issue needs to hear some feedback from the users of lynt.
Milestone

Comments

@saadq
Copy link
Owner

saadq commented Feb 6, 2019

Before releasing v1, I am thinking about making lynt's rules a lot more relaxed and to truly only check for errors (this would be using @suchipi's eslint-config-unobtrusive which I had initially rejected in #1). This would mean that rules like no-var, eqeqeq, prefer-const, curly etc which aren't really checking for errors but rather check for "best practices" would be turned off. The idea is that any JS/TS codebase should be able to use lynt's default config, regardless of a person's coding style and whether they are using an ES6 codebase or not.

With the --strict flag enabled, only then are these "best practices" rules turned on. Curious to hear thoughts on this.

@saadq saadq added enhancement New feature or request. feedback wanted This issue needs to hear some feedback from the users of lynt. labels Feb 6, 2019
@tunnckoCore
Copy link

Hm. That separation sounds good, yea.

@saadq saadq added this to the Lynt v1 milestone Feb 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request. feedback wanted This issue needs to hear some feedback from the users of lynt.
Projects
None yet
Development

No branches or pull requests

2 participants