-
Notifications
You must be signed in to change notification settings - Fork 515
[meta] Implement all styles that are being dropped from JSHint #102
Comments
👍 |
2 similar comments
+1 |
👍 |
So far, the only one that looks like it'll be difficult to implement is |
BTW, @mdevils, I promise to support and maintain all of these checks, besides for just contributing the initial features. |
This is awesome |
8 pull requests in... just 4 more to go! |
👍 |
I am very glad to hear. I working on a document for maintainers and would be glad if you join as a maintainer. You pull-requests are clear and straight. |
Reviewed pull requests. Accepted some, put comments to other. |
@mdevils, I'd love to be a maintainer. Just let me know what you'd like me to do and I look forward to the maintainer's document. |
Found one more hiding: |
@mdevils, still working on |
indent posted. That's all of them! |
Woooo! |
Woohoo! All Merged! |
Found one more, @mdevils. This is the last of them. |
That's fantastic! 🍰 |
We are almost there 👍 |
I guess we can close this issue and release a new version? |
We can. I'd ideally like to make a Perhaps we should cut the new version now as a release candidate, so people can start using it and giving us feedback, and then do a real release with documentation and any bug fixes we find in rc. @mdevils Thoughts? |
Done 😉 |
Version |
This is just awesome. Thanks for you works guys ! |
Not sure if |
https://github.com/jshint/jshint/blob/37757f0195e9ee4eb4bd8aeb5162c2a3c1565832/src/options.js#L45 plusplus is surviving to 3.0 Our design goals have always been to compliment JSHint, rather than duplicate it, so we're not going to implement this one. @antonkovalyov, you guys are keeping @nschonni also, if it turns out it is being cut, please open a new issue instead of appending onto this one. Thanks! |
I don't remember why I kept it. I'll re-visit it and will let you know asap. |
Don't merge yet - feedback wanted. JSHint people want to focus on syntax linting and are dropping style oriented options. They recommends using JSCS (in addition to JSHint) for style: jshint/jshint#1339 JSCS has recently added the options dropped from JSHint. jscs-dev/node-jscs#102 This commit contains a JSCS config file with some basic settings that generate very few errors with the existing cordova-cli and lib code. Would be glad to get some feedback about this. My goal is to eventually run JSCS together with JSHint as part of `npm test`. The nice thing about JSCS is that style flame wars can be way more structured with it as we can argue about very specific well named JSCS config options :) I'm using it with SublimeLinter-jscs https://sublime.wbond.net/packages/SublimeLinter-jscs
Don't merge yet - feedback wanted. JSHint people want to focus on syntax linting and are dropping style oriented options. They recommends using JSCS (in addition to JSHint) for style: jshint/jshint#1339 JSCS has recently added the options dropped from JSHint. jscs-dev/node-jscs#102 This commit contains a JSCS config file with some basic settings that generate very few errors with the existing cordova-cli and lib code. Would be glad to get some feedback about this. My goal is to eventually run JSCS together with JSHint as part of `npm test`. The nice thing about JSCS is that style flame wars can be way more structured with it as we can argue about very specific well named JSCS config options :) I'm using it with SublimeLinter-jscs https://sublime.wbond.net/packages/SublimeLinter-jscs
But not running it as part of `npm test` yet. See discussion here: http://markmail.org/thread/rzzvn2ax3tqzabfw JSHint people want to focus on syntax linting and are dropping style oriented options. They recommends using JSCS (in addition to JSHint) for style: jshint/jshint#1339 JSCS has recently added the options dropped from JSHint. jscs-dev/node-jscs#102 This commit contains a JSCS config file with some basic settings that generate very few errors with the existing cordova-cli and lib code. My goal is to eventually run JSCS together with JSHint as part of `npm test`. The nice thing about JSCS is that style flame wars can be way more structured with it as we can argue about very specific well named JSCS config options :) I'm using it with SublimeLinter-jscs https://sublime.wbond.net/packages/SublimeLinter-jscs
But not running it as part of `npm test` yet. See discussion here: http://markmail.org/thread/rzzvn2ax3tqzabfw JSHint people want to focus on syntax linting and are dropping style oriented options. They recommends using JSCS (in addition to JSHint) for style: jshint/jshint#1339 JSCS has recently added the options dropped from JSHint. jscs-dev/node-jscs#102 This commit contains a JSCS config file with some basic settings that generate very few errors with the existing cordova-cli and lib code. My goal is to eventually run JSCS together with JSHint as part of `npm test`. The nice thing about JSCS is that style flame wars can be way more structured with it as we can argue about very specific well named JSCS config options :) I'm using it with SublimeLinter-jscs https://sublime.wbond.net/packages/SublimeLinter-jscs
Great! |
But not running it as part of `npm test` yet. See discussion here: http://markmail.org/thread/rzzvn2ax3tqzabfw JSHint people want to focus on syntax linting and are dropping style oriented options. They recommends using JSCS (in addition to JSHint) for style: jshint/jshint#1339 JSCS has recently added the options dropped from JSHint. jscs-dev/node-jscs#102 This commit contains a JSCS config file with some basic settings that generate very few errors with the existing cordova-cli and lib code. My goal is to eventually run JSCS together with JSHint as part of `npm test`. The nice thing about JSCS is that style flame wars can be way more structured with it as we can argue about very specific well named JSCS config options :) I'm using it with SublimeLinter-jscs https://sublime.wbond.net/packages/SublimeLinter-jscs
But not running it as part of `npm test` yet. See discussion here: http://markmail.org/thread/rzzvn2ax3tqzabfw JSHint people want to focus on syntax linting and are dropping style oriented options. They recommends using JSCS (in addition to JSHint) for style: jshint/jshint#1339 JSCS has recently added the options dropped from JSHint. jscs-dev/node-jscs#102 This commit contains a JSCS config file with some basic settings that generate very few errors with the existing cordova-cli and lib code. My goal is to eventually run JSCS together with JSHint as part of `npm test`. The nice thing about JSCS is that style flame wars can be way more structured with it as we can argue about very specific well named JSCS config options :) I'm using it with SublimeLinter-jscs https://sublime.wbond.net/packages/SublimeLinter-jscs
As of JSHint 3.0, all style conformance rules are being dropped: jshint/jshint#1339 . JSCS is the perfect tool to reimplement these checks. Hopefully, all can be implemented, as this will help a lot with adoption of JSCS as the defacto style checker.
Here's all the options being dropped:
multistr
rule. #141 http://www.jshint.com/docs/options/#multistr...
The text was updated successfully, but these errors were encountered: