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
We're using a script to set up our development environment. That script creates Eclipse configurations for plugins, including JSHint in .settings/com.eclipsesource.jshint.ui.prefs.
However, for JSHint to be enabled, a developer must still open the JSHint preferences for each project, modify something in the JSHint settings and save.
Is that a bug, or are we missing something?
The text was updated successfully, but these errors were encountered:
Saving the settings will add the builder com.eclipsesource.jshint.ui.builder to the .project file. If the builder is missing, the JSHint validator will not run. This issue is related to #29.
We're using a script to set up our development environment. That script creates Eclipse configurations for plugins, including JSHint in .settings/com.eclipsesource.jshint.ui.prefs.
Our prefs file looks like this:
However, for JSHint to be enabled, a developer must still open the JSHint preferences for each project, modify something in the JSHint settings and save.
Is that a bug, or are we missing something?
The text was updated successfully, but these errors were encountered: