What problem does this feature solve?
We are migrating the storybook-rsbuild monorepo from Biome to Rslint. Almost all of our previous lint policy mapped 1:1 onto Rslint's existing rules — the one gap left on the React side is react/jsx-no-useless-fragment.
The rule is already listed (unchecked) in the eslint-plugin-react tracking issue #225, so this is a request to prioritize it. Reasons it pulls ahead of the rest of the backlog:
What does the proposed API of configuration look like?
Same as upstream eslint-plugin-react, no new API surface:
rules: {
'react/jsx-no-useless-fragment': ['warn', { allowExpressions: true }],
}
Options to match upstream: allowExpressions (default false).
What problem does this feature solve?
We are migrating the storybook-rsbuild monorepo from Biome to Rslint. Almost all of our previous lint policy mapped 1:1 onto Rslint's existing rules — the one gap left on the React side is
react/jsx-no-useless-fragment.The rule is already listed (unchecked) in the eslint-plugin-react tracking issue #225, so this is a request to prioritize it. Reasons it pulls ahead of the rest of the backlog:
errorlevel (rules/react.js), and it has been ported by Biome (asnoUselessFragments) and by Oxlint (react/jsx-no-useless-fragment). Migrations from either tool hit this gap immediately.What does the proposed API of configuration look like?
Same as upstream eslint-plugin-react, no new API surface:
Options to match upstream:
allowExpressions(defaultfalse).