-
Notifications
You must be signed in to change notification settings - Fork 6
--strict mode #35
Copy link
Copy link
Open
Labels
enhancementNew feature or request.New feature or request.feedback wantedThis issue needs to hear some feedback from the users of lynt.This issue needs to hear some feedback from the users of lynt.
Milestone
Description
Metadata
Metadata
Assignees
Labels
enhancementNew feature or request.New feature or request.feedback wantedThis issue needs to hear some feedback from the users of lynt.This issue needs to hear some feedback from the users of lynt.
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-unobtrusivewhich I had initially rejected in #1). This would mean that rules likeno-var,eqeqeq,prefer-const,curlyetc 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
--strictflag enabled, only then are these "best practices" rules turned on. Curious to hear thoughts on this.