8000 Explain UTF-8 BOM rule in readme · Issue #1640 · airbnb/javascript · GitHub
[go: up one dir, main page]

Skip to content
Explain UTF-8 BOM rule in readme #1640
Open
@mk-pmb

Description

@mk-pmb

Most style decisions are explained in the readme, but I couldn't find the reasoning on why a BOM is considered bad. Where I've looked:

  • the patch that enabled it, found no commit message body.
  • the current code of the rules file,
    // require or disallow the Unicode Byte Order Mark
    // https://eslint.org/docs/rules/unicode-bom
    'unicode-bom': ['error', 'never'],
  • the eslint rule page mentioned in the patch code comment, doesn't claim it's bad.
  • searched the readme for "BOM", "unicode" and "byte order"
  • searched issue tracker for "BOM", "unicode" and "byte order"

Could someone explain it, or add search keywords to make the explanation easier to find?

Update: Also, is there a recommendation on how to declare the file encoding instead? I searched the readme for "charset", "encod" and "character set" but no matches.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0