Open Munter opened 11 years ago
I've ignored all jshint magic on purpose. Jshnt does all file-system operations synchronous AND sequentially.
The other part of the problem is that jshint configuration (within slint) would behave differently from all other linters within slint.
I would much rather have slint have shims/compatibility-layers to behave more like jshint/whatever out there. (We could even supply a jshint
-binary that behaves like jshint, apart from running a lot more linters.
jshint has built in ways to define configuration and ignores using
.jshintrc
and.jshintignore
.There are several external tools, like sublime-linter, which leverage these files to improve developer feedback inside editors etc.
Jshint itself also uses these files unless you specifically override the configuration.
It seems to me that there would be a lot of value gained to hook into this ecosystem which other tools seem to be standardizing on as well, so slint can plug right into an existing project without extra configuration.