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

Can't specify command line options to jshint? #15

Open
jxtps opened this issue Jul 30, 2014 · 3 comments
Open

Can't specify command line options to jshint? #15

jxtps opened this issue Jul 30, 2014 · 3 comments

Comments

@jxtps
Copy link

jxtps commented Jul 30, 2014

I need to disable some of the warnings (which for some reason seem to be interpreted as errors by Play?!), but they don't have explicit names. The technique for doing that is outlined on http://www.jshint.com/docs/ - just add the --verbose flag to the command line.

But how do I do that in sbt-jshint?

Reading https://github.com/sbt/sbt-jshint/blob/master/src/main/scala/com/typesafe/sbt/jshint/SbtJSHint.scala and https://github.com/sbt/sbt-jshint/blob/master/src/main/resources/jshint-shell.js seems to indicate that it's not currently possible?

@huntc
Copy link

huntc commented Jul 31, 2014

Please note the last para of the README:

Options can be specified in accordance with the JSHint website and they share the same set of defaults. To set an option you can provide a .jshintrc file within your project's base directory. If there is no such file then a .jshintrc file will be search for in your home directory. This behaviour can be overridden by using a JshintKeys.config setting for the plugin. JshintKeys.config is used to specify the location of a configuration file.

@huntc huntc closed this as completed Jul 31, 2014
@jxtps
Copy link
Author

jxtps commented Jul 31, 2014

Yes, I can specify the options using the .jshintrc, but not the command_line options!?

(the --verbose flag doesn't appear to be possible to specify in the .jshintrc file?)

@huntc
Copy link

huntc commented Jul 31, 2014

I see - sorry for not reading properly. PRs are welcome. :-)

@huntc huntc reopened this Jul 31, 2014
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

2 participants