Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upNew rule: unicode-bom #538
Comments
feross
added
the
enhancement
label
Jun 2, 2016
This comment has been minimized.
This comment has been minimized.
dougwilson
commented
Jun 2, 2016
|
What is the suggested value for the rule? |
This comment has been minimized.
This comment has been minimized.
|
Yep. Setting it to |
This comment has been minimized.
This comment has been minimized.
|
I'm only like half-understanding this rule; not spotting any way it affects anything I've ever done with JS so |
This comment has been minimized.
This comment has been minimized.
|
@yoshuawuyts See #283 for some more context, if you're interested. |
feross
modified the milestone:
v8
Jul 12, 2016
feross
closed this
in
standard/eslint-config-standard@e5e37a9
Jul 12, 2016
This comment has been minimized.
This comment has been minimized.
|
This rule will be included in standard v8 |
Merged
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.
feross commentedJun 2, 2016
http://eslint.org/docs/rules/unicode-bom
This was previously covered by
no-irregular-whitespacebut BOM characters at the beginning of files are now stripped by eslint, so adding this rule just gets us the old behavior again.