Skip to content
This repository has been archived by the owner on Mar 23, 2024. It is now read-only.

[meta] Implement all styles that are being dropped from JSHint #102

Closed
17 tasks done
mikesherov opened this issue Dec 26, 2013 · 29 comments
Closed
17 tasks done

[meta] Implement all styles that are being dropped from JSHint #102

mikesherov opened this issue Dec 26, 2013 · 29 comments

Comments

@mikesherov
Copy link
Contributor

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:

...

@sindresorhus
Copy link
Contributor

👍

2 similar comments
@doberkofler
Copy link

+1

@hnrch02
Copy link

hnrch02 commented Dec 29, 2013

👍

@mikesherov
Copy link
Contributor Author

So far, the only one that looks like it'll be difficult to implement is indent if we're trying to be smart about it, and trying to enforce some kind of ruleset about when to indent. Much easier would be simply to check that if something is indented or outdented that the right character is being used and the right number of spaces / tabs are used.

@mikesherov
Copy link
Contributor Author

BTW, @mdevils, I promise to support and maintain all of these checks, besides for just contributing the initial features.

@markelog
Copy link
Member

This is awesome

@mikesherov
Copy link
Contributor Author

8 pull requests in... just 4 more to go!

@mdevils
Copy link
Member

mdevils commented Dec 30, 2013

👍

@mdevils
Copy link
Member

mdevils commented Dec 30, 2013

BTW, @mdevils, I promise to support and maintain all of these checks, besides for just contributing the initial features.

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.

@mdevils
Copy link
Member

mdevils commented Dec 30, 2013

Reviewed pull requests. Accepted some, put comments to other.

@mikesherov
Copy link
Contributor Author

@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.

@mikesherov
Copy link
Contributor Author

Found one more hiding: maxlen

@mikesherov
Copy link
Contributor Author

@mdevils, still working on indent, which is a bit more complex than the rest, but making good progress. Hope to have it done in the next few days! We should plan a release for when these final options land :-)

@mikesherov
Copy link
Contributor Author

indent posted. That's all of them!

@sindresorhus
Copy link
Contributor

Woooo!

@mikesherov
Copy link
Contributor Author

Woohoo! All Merged!

@mikesherov
Copy link
Contributor Author

Found one more, @mdevils. This is the last of them.

@passy
Copy link

passy commented Jan 8, 2014

That's fantastic! 🍰

@mdevils
Copy link
Member

mdevils commented Jan 9, 2014

We are almost there 👍

@mdevils
Copy link
Member

mdevils commented Jan 9, 2014

I guess we can close this issue and release a new version?

@mikesherov
Copy link
Contributor Author

We can. I'd ideally like to make a jshint preset and a migration guide, as in #138 .

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?

@mikesherov
Copy link
Contributor Author

@mdevils, also, before we cut a new version, can you merge this please: #148

@mdevils
Copy link
Member

mdevils commented Jan 9, 2014

Done 😉

@mdevils
Copy link
Member

mdevils commented Jan 9, 2014

Version 1.2.0 is released. Thanks to Mike Sherov!

@mdevils mdevils closed this as completed Jan 9, 2014
@MoOx
Copy link

MoOx commented Jan 13, 2014

This is just awesome. Thanks for you works guys !

@nschonni
Copy link
Contributor

Not sure if plusplus is on the chopping block, but it might be a good fit here.

@mikesherov
Copy link
Contributor Author

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 plusplus, right?

@nschonni also, if it turns out it is being cut, please open a new issue instead of appending onto this one. Thanks!

@valueof
Copy link

valueof commented Jan 18, 2014

I don't remember why I kept it. I'll re-visit it and will let you know asap.

kamrik added a commit to kamrik/cordova-lib that referenced this issue Aug 1, 2014
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
kamrik added a commit to kamrik/cordova-lib that referenced this issue Aug 1, 2014
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
asfgit pushed a commit to apache/cordova-lib that referenced this issue Aug 6, 2014
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
asfgit pushed a commit to apache/cordova-lib that referenced this issue Sep 5, 2014
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
@popomore
Copy link

Great!

matt-oakes pushed a commit to matt-oakes/cordova-lib-watchos that referenced this issue Apr 3, 2017
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
matt-oakes pushed a commit to matt-oakes/cordova-lib-watchos that referenced this issue Apr 3, 2017
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
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests