Sindre Sorhus

> eslint-unicorn flat eslint-config-unicorn non flat? That was my idea too. However, `eslint-config-unicorn` would not receive any further updates.

@zeorin Options should be in camelcase. `jsxFilenameCase` is not descriptive enough either I would say. How about `{useJsxConvention: true}`?

> Thinking about this a little more, what happens when there are components that start with a lowercase letter? Higher order components do this quite frequently, and whilst most probably...

Just to be clear. This will detect actual JSX usage in a file. Not the `.jsx` file extension, [which is discouraged](https://twitter.com/dan_abramov/status/763712190272667648?lang=en).

> And I prefer const foo = '\u007A'; over const foo = '\u{7A}'; Did you see my arguments for why `\u{7A}` is better? It's shorter and it lets you use...

> About the name, we already have better-regex, let's use better-string? I forgot to mention, it should apply to regexes too. I think it's better to have an explicit name...

> This overlaps with the no-hex-escapes rule. Not sure whether we should deprecate that one. It's plausible that someone wants to prevent Hex escapes, but not prefer code point escapes....

This is now accepted.

> If we extend the rule to RegExp we also have to make sure at least u flag is used during autofix 👍 > should we only focus on string?...

https://github.com/sindresorhus/eslint-plugin-unicorn/pull/2414#discussion_r1696783852 was not resolved.