There are a few scenarios where you want to avoid string literals in JSX. You may want to enforce consistency, reduce syntax highlighting issues, or ensure that strings are part of a translation system.
By default this rule requires that you wrap all literal strings in a JSX container {'TEXT'}.
The following patterns are considered warnings:
var Hello = <div>test</div>;The following patterns are not considered warnings:
var Hello = <div>{'test'}</div>;var Hello = <div>
{'test'}
</div>;There are two options:
noStrings(default:false) - Enforces no string literals used as children, wrapped or unwrapped.allowedStrings- An array of unique string values that would otherwise warn, but will be ignored.ignoreProps(default:false) - Whentruethe rule ignores literals used in props, wrapped or unwrapped.
To use, you can specify as follows:
"react/jsx-no-literals": [<enabled>, {"noStrings": true, "allowedStrings": ["allowed"], "ignoreProps": false}]In this configuration, the following are considered warnings:
var Hello = <div>test</div>;var Hello = <div>{'test'}</div>;var Hello = <div>
{'test'}
</div>;var Hello = <div class='xx' />;var Hello = <div class={'xx'} />;var Hello = <div class={`xx`} />;The following are not considered warnings:
// When using something like `react-intl`
var Hello = <div><Text {...message} /></div>// When using something similar to Rails translations
var Hello = <div>{translate('my.translation.key')}</div>// an allowed string
var Hello = <div>allowed</div>// an allowed string surrounded by only whitespace
var Hello = <div>
allowed
</div>;// spread props object
var Hello = <Text {...props} />// use variable for prop values
var Hello = <div class={xx} />// cache
class Comp1 extends Component {
asdf() {}
render() {
return (
<div onClick={this.asdf}>
{'asdjfl'}
test
{'foo'}
</div>
);
}
}If you do not want to enforce any style JSX literals, then you can disable this rule.