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

Read a config file on the fly #81

Open
wallet77 opened this issue Feb 26, 2014 · 2 comments
Open

Read a config file on the fly #81

wallet77 opened this issue Feb 26, 2014 · 2 comments

Comments

@wallet77
Copy link

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.

@ralfstx
Copy link
Member

ralfstx commented Feb 26, 2014

We should figure out if this can be done with an IResourceChangeListener.

@freethejazz
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants