[Bug]: allowExpression in react/jsx-no-useless-fragment

[YuriyDyachkov]

Is there an existing issue for this?

• [X] I have searched the existing issues and my issue is unique
• [X] My issue appears in the command-line and not only in the text editor

Description Overview

I added the allowExpression: true option to my config, but the empty fragment still shows the error.

Expected Behavior

There shouldn't be any mistakes. What did I miss?

eslint-plugin-react version

7.32.2

eslint version

8.15.0

node version

16

[ljharb]

“nothing” isn’t an expression.

Why return an empty fragment instead of undefined or null?