-
Notifications
You must be signed in to change notification settings - Fork 113
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
Replace JSChecker with Java version that plugs into compiler #41
Comments
This isn't actually going to be able to lint Closure Style due to a bug google/closure-compiler/pull/1768. This linter also doesn't check things like how two blank lines need to be before members, and three blank lines need to be before constructors. So I don't think it's really a replacement for the Python linter quite yet. However this would be REALLY GOOD for incrementally checking the syntax of JavaScript code, because it goes lightning fast. So I'm repurposing this bug. |
@jart Thanks. I was under the impression from the following resources that linter.jar/clang-format was the new best practice internally at Google.
Am I moving too quickly in assuming that gjslint is deprecated / is in the process of being deprecated? To the best of your knowledge, do any plans exist to update gjslint with support for ES6? Should new code be written per the formatting guidelines of gjslint or linter.jar/clang-format? Would clang-format (in addition to linter.jar) address your concerns about blank lines before members/constructors? |
I don't know what's up with linter.jar but there's other stuff I'm already doing like jschecker.py. So I'm thinking we shouldn't use linter.jar. We could just write a Java program that plugs directly in the Closure Compiler, does the linting, validation, strict dependency checking, and all that good stuff. What do you think? |
@jart Thanks, that sounds good to me. |
The current linter rule (closure_js_lint_test) uses the deprecated python closure-linter instead of the the new linter.jar (which is open sourced in the closure-compiler repository). The new linter has better support for ES6.
Can closure_js_lint_test be upgraded to use the new linter?
The text was updated successfully, but these errors were encountered: