@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 firstname.lastname@example.org, 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 email@example.com
@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?
Just read the article you wrote on Medium @markelog. Had a little heartache while reading it. It must be hard to let your baby goes that way guys. Thanks all for the hard work you put into that project to make it what it is today. Thanks as well for your help towards little contributors as I.
JSCS 3.0.3 seems to generate spurious error messages and break my webpack build.