[bug] HTML characters should be allowed inside of `no-useless-fragment`

[imjordanxd]

Describe the bug

The following code produces an error but is a false positive:

function Foo() {
    return <>&nbsp;</>;
}

Reproduction

No response

Expected behavior

An error should not be reported in this case.

Platform and versions

Node 20.18.0
@eslint-react 1.15.0

Stack trace

No response

Additional context

No response

[SukkaW]

Any more reproduction?

With React 18.3+ and TypeScript 5.4+, it is possible to return a string in a Component now. Your current reproduction can be simplified without fragments:

function Foo() {
  return ' ';
}

[imjordanxd]

@SukkaW unfortunately, that won't work.   is a reserved entity in HTML. React handles strings for us. It's the same reason we can't return '<div>Hello, world</div>'. We wouldn't expect that to work! Here's a codesandbox.

[SukkaW]

@SukkaW unfortunately, that won't work.   is a reserved entity in HTML. React handles strings for us. It's the same reason we can't return '<div>Hello, world</div>'. We wouldn't expect that to work! Here's a codesandbox.

Then it would be:

function Foo() {
  return ' ';
}

or

function Foo() {
  return '\xA0';
}

Most modern compilers (esbuild, swc) will transform alone  .