You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we use a version control system, we want to save jshint's config file. But if a modification is done on that file the JsHint eclipse plugin will not take it into account cause there is only an "import" system.
So all users need to re-import the new file with modifications.
It could be nice to be able to link jshint plugin with a config file and each time the plugin is launched it reads the configuration in that file.
The text was updated successfully, but these errors were encountered:
EDIT
I might be confusing things, but wasn't this available in 0.9.8, but the .jshintrc file had to be in the project root? Looks like it works from #61 ...
ENDEDIT
+1 for this. It's more complex, but IntelliJ handles this pretty well (and dynamically) with a use config option:
Select this check box to have the code verified according to the settings from a configuration file. A configuration file is a JSON file with the extension .jshintrc that specifies which JSHint options should be enabled or disabled. IntelliJ IDEA will look for a .jshintrc file in the working directory. If the search fails, IntelliJ IDEA will search in the parent folder, then again in the parent folder. The process is repeated until IntelliJ IDEA finds a .jshintrc or reaches the project root. To have IntelliJ IDEA still run verification in this case, specify the default configuration file to use.
When we use a version control system, we want to save jshint's config file. But if a modification is done on that file the JsHint eclipse plugin will not take it into account cause there is only an "import" system.
So all users need to re-import the new file with modifications.
It could be nice to be able to link jshint plugin with a config file and each time the plugin is launched it reads the configuration in that file.
The text was updated successfully, but these errors were encountered: