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

New rule: unicode-bom #538

Closed
feross opened this Issue Jun 2, 2016 · 5 comments

Comments

3 participants
@feross
Copy link
Member

commented Jun 2, 2016

http://eslint.org/docs/rules/unicode-bom

This was previously covered by no-irregular-whitespace but BOM characters at the beginning of files are now stripped by eslint, so adding this rule just gets us the old behavior again.

@feross feross added the enhancement label Jun 2, 2016

@dougwilson

This comment has been minimized.

Copy link

commented Jun 2, 2016

What is the suggested value for the rule? "never" I assume?

@feross

This comment has been minimized.

Copy link
Member Author

commented Jun 2, 2016

Yep. Setting it to "never" would match the old behavior of the no-irregular-whitespace rule.

@yoshuawuyts

This comment has been minimized.

Copy link
Contributor

commented Jun 2, 2016

I'm only like half-understanding this rule; not spotting any way it affects anything I've ever done with JS so 👍 I guess

@feross

This comment has been minimized.

Copy link
Member Author

commented Jun 2, 2016

@yoshuawuyts See #283 for some more context, if you're interested.

@feross feross modified the milestone: v8 Jul 12, 2016

@feross feross referenced this issue Jul 12, 2016

Closed

Release proposal: standard v8 #564

16 of 16 tasks complete
@feross

This comment has been minimized.

Copy link
Member Author

commented Jul 12, 2016

This rule will be included in standard v8

@lock lock bot locked as resolved and limited conversation to collaborators May 10, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.