`text-encoding-identifier-case` error in JSX; `utf8` is not valid HTML

[jp-knj]

According to WhatWG, the value must be an ASCII case-insensitive match for "UTF-8"

please text-encoding-identifier-case of rule check
Thanks for always helping us out

example
This is causing conflicts in our React code (in .tsx files that are linted by eslint):

<form
  id="search_keyword"
  method="get"
  action={action}
  acceptCharset="UTF-8" // get eslint error
>
  <input
    type="search"
    name="q"
    id="q"
  />
        ....
</form>

[Pyrolistical]

Similarly new TextDecoder("utf-8") is another false positive as according to the spec:

Authors must use the UTF-8 encoding and must use its (ASCII case-insensitive) "utf-8" label to identify it.

utf-8 is canonical

[fisker]

It's hard to check places that only allows utf-8, but utf-8 works everywhere (I think), how about we switch from utf8 to use utf-8?

Mentioned this problem in original proposal, #1690 (comment)

[timdavish]

It's hard to check places that only allows utf-8, but utf-8 works everywhere (I think), how about we switch from utf8 to use utf-8?

Mentioned this problem in original proposal, #1690 (comment)

Does it make sense to make this configurable, at a minimum? I know you originally proposed configurability here: #1690 (comment)

[fisker]

Make sense to me.

[carlosjeurissen]

Situations exist in which utf8 is the default, and utf-8 is an alias like in nodeJS:
https://nodejs.org/api/buffer.html#buffers-and-character-encodings

However, considering utf-8 is required in more situations this seems the best option.

The following PR changes the default to utf-8: #2600

[carlosjeurissen]

@sindresorhus:

The convention in Node.js (and as used in most Node.js docs) is utf8, and I don't see any reason to break that. I'm not against adding an option to support utf-8, but the default should continue to be utf8 (in our docs and code too).

Using this thread for further discussion. You feel specifically for nodeJS code (like fs.readFile), utf8 should be preferred instead of utf-8? Or in general this eslint plugin should always default to utf8 unless a user decides otherwise? (except for cases in which utf8 is not supported, like in #2547)

[sindresorhus]

I prefer it to always default to utf8 except the one case it cannot, unless the user has chosen to prefer utf-8.

[fisker]

{
	whatwgEncoding: boolean;
}

?