hound: Hound does not respect tests/.jshintrc
Currently Hound only supports a single JSHint config, even though standard usage in most products is to provide a different .jshintrc for tests than what’s used for app code. This allows developers to declare globals that SHOULD throw warnings in app code (such as test framework methods) while ignoring them inside of tests. As far as I can tell, there is no way to configure Hound to respect the test config.
About this issue
- Original URL
- State: open
- Created 9 years ago
- Reactions: 3
- Comments: 17 (6 by maintainers)
I’ve closed my prior ticket (which is the same issue, different reasons) and putting in my two cents here (copied from the other ticket):
Relevant comment 1: ESLint mentions that config files can have hierarchy and cascade. http://eslint.org/docs/user-guide/configuring#configuration-cascading-and-hierarchy This doesn’t appear to work at all with Hound. Is there a reason this doesn’t work?
Relevant comment 2: Node projects [are a use case where different config files are needed for different folders]. Don’t enable, for example,
browseron the server environment. But enable it for any client js. Vice versa, don’t enablenodein the client.Thanks.
(Closed ticket: #1210.)