Skip to content
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

JSCS configuration files as formatting rules. #3

Open
ghost opened this issue Sep 26, 2014 · 4 comments
Open

JSCS configuration files as formatting rules. #3

ghost opened this issue Sep 26, 2014 · 4 comments

Comments

@ghost
Copy link

ghost commented Sep 26, 2014

Here's just a thought, enchancement of some sort.

You can use .jscsrc files from node-jscs in your plugin thus giving it more functionality ;). We use jscs in our company and it helped a lot setting one style in team and keeping it that way.

https://github.com/jscs-dev/node-jscs - here's link to repo.

@paulirish
Copy link
Collaborator

Yeah currently the rulesets for esformatter and jscs are not compatible. I do think someone could write a translator, though..

@paulirish
Copy link
Collaborator

If anyone is interested in creating a utility that can bridge the configuration of jscs and jsfmt, that'd be super useful!

@AuthorProxy
Copy link

Please use standard format of configuration files .jshint and .jscs, well-formed and unified across all developers. Don't construct your own bicycle for this. Thanks for your work.

@paulirish
Copy link
Collaborator

This has to happen upstream in Miller's projects but I think the idea
itself is really good.

At the very least we should have a utility that can translate between the
two rule formats.

On Tue, Nov 18, 2014 at 8:38 AM, Alex V. Kostyukov <[email protected]

wrote:

Please use standard format of configuration files .jshint and .jscs,
well-formed and unified across all developers. Don't construct your own
bicycle for this. Thanks for your work.


Reply to this email directly or view it on GitHub
#3 (comment)
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants