Can we modify jscs config locally for a project, pretty much as a .jscsrc or something alike?
so we could work on project with different coding style that our default without having all the code base in red.
@Nargonath not sure i understand, jscs config is .jscsrc file, you can modify as you like, or you can change .editorconfig
@markelog Perhaps I'm a bit confused as I'm not using jscs directly but through the Atom's plugin. I cannot change the .editorconfig because I'm not the one who decides it settings.
@markelog Looking at the local node-jscs project I have, I don't have any errors in the files even though my default preset is "google" and the editorconfig specifies 4 spaces indent style. The only difference with the previous project I mentioned is that it has the .jscsrc. I think that's what was missing from it. I got my answer. Sorry for disturbing. :)
Is there a doc that mentions the .jscsrc? Didn't find any :/. Perhaps I didn't look good enough.
@markelogjscs-dev/node-jscs#2202 Please let me know what you think
@indexzero in master or in 2.x?
@ValYouW i will, right now there is a lot to do, i probably check it out today or maybe tomorrow
thanks for the pull btw
@markelog 2.11.0 looks to be a babylon bug exposed through babel-jscs. The AST node has the raw value (e.g. '&LA;
But the TOKEN has the unescaped value
And I can't figure out where the token is created from the node
oh, we use parser tokenizer
so it should be from there
i.e. yeah, it should be babylon behaviour
@markelog@hzoo logged the bug as best I could determine it against babel-jscs. I don’t know if this is fixed in the 3.0.0-beta, but hopefully this gives you the information to see if this edge case persists as we move to babylon@6
No problem. This is such a mind$%^& I hope you can figure it out
I could not figure out how onTokens get populated by babylon in email@example.com, but I can see that @hzoo is using in the 3.0.0-beta
@hzoo I meant to say you’re using a different technique than onToken in firstname.lastname@example.org
@indexzero Question: shall I make the global or local .jscsignore files optional (in the CLI for instance)?
Yes, a .jscsignore would always be optional. But if it exists in the local directory it would be used implicitly. Just like a .gitignore
Is it possible to run jscs over .json and --fix errors?