Having JSHint installed makes it problematic to hack on Brackets

[busykai]

Recent support for multiple providers in Code Inspection overrides JSLint default linter in any other linter for JavaScript is installed. Recognizing it's a temporary solution, it makes it impossible to hack on Brackets with JSHint installed.

It makes it very inconvenient to work on two repositories one of which uses JSHint and the other which uses JSLint. Getting credible (as per configuration) JSLint output requires uninstalling JSHint.

[peterflynn]

Fwiw, this was true before the multiple linters change as well: registering JSHint has always overwritten the JSLint provider.

[pthiess]

@ingorichter Please take a look at the potential effort. It might be a move to backlog, but I call it a medium priority for now.

[pthiess]

@ingorichter Please make sure you follow up with @busykai since he seems to be working on this already, @dangoor may have additional input too. It seems as if @busykai is not a committer yet so I assigned it to you to help as needed.

[busykai]

@ingorichter , I'd like to take this one (if next week is fine). we had some discussion with @peterflynn and @dangoor in #6662 and, if I am not mistaken, there seems an agreement on how this should be approached.

[ingorichter]

@busykai @dangoor @peterflynn reading #6222 gives me the impression, that we want to implement a solution that doesn't have any UI impact for now? I remember a conversation, where we thought about having some UI to enable/disable linter for a specific filetype. I agree, that this will be backed by preferences and enables us to change behavior on a more fine grained level (project, directory, file).

[busykai]

@ingorichter you're right, the discussion was around how the options should be structure without any impact on the UI. as far as I understand, once the UI is there for the preferences, it will be straightforward to expose them. @dangoor, @peterflynn, am i missing something?

[peterflynn]

@busykai Right, that was my impression of the conversation too: start by adding bare preferences to turn individual linting providers on/off (which would let you have e.g. a project pref in the Brackets src project to turn off JSHint & turn on JSLint, while having the reverse settings be the default for all your other projects). And then later we could introduce UI for it once we start getting more into UI for preferences generally.