Skip to content

Latest commit

 

History

History
82 lines (58 loc) · 1.69 KB

jsx-no-literals.md

File metadata and controls

82 lines (58 loc) · 1.69 KB

Prevent usage of string literals in JSX (react/jsx-no-literals)

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.

Rule Details

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>;

Rule Options

There are two options:

  • noStrings - 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.

To use, you can specify as follows:

"react/jsx-no-literals": [<enabled>, {"noStrings": true, "allowedStrings": ["allowed"]}]

In this configuration, the following are considered warnings:

var Hello = <div>test</div>;
var Hello = <div>{'test'}</div>;
var Hello = <div>
  {'test'}
</div>;

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>;

When Not To Use It

If you do not want to enforce any style JSX literals, then you can disable this rule.