Is there an equivalent rule to react/jsx-no-literals, or why do we not need it?

[daggmano]

We try to ensure all our displayed text is handled by react-intl in order to prepare us for eventual internationalization. Moving to biome, there does not seem to be an equivalent to react/jsx-no-literals. As a new biome user I'm not sure I'm ready to write a plugin to do this, but perhaps someone else has already faced this one? Or has a reason why such a rule is unnecessary?

[arendjr]

Given that we've closed #3 in favour of rule suggestion discussions, I'm reopening this one :)

[ysulyma]

Just migrated my team from ESLint/Prettier to Biome v2, but we still need ESLint to enforce react/jsx-no-literals. We use this rule for two purposes:

• ensuring strings are extracted for future internationalization
• ensuring UI strings are available for tests

[EdenTurgeman]

Just switched from ESLint/Prettier to Biome v2 for our company and this rule is missed dearly.

[ematipico]

Closing #724

[mateus4k]

I think this should be reopened since #724 was closed, @ematipico.

[ematipico]

I linked the wrong issue. The rule has been implemented

[mateus4k]

Oh, great! What's the name of the rule? I couldn't find it

[mateus4k]

I just found it. It's noJsxLiterals:

"nursery": {
    "noJsxLiterals": "error"
}