Ensure correct position of the first property.
Fixable: This rule is automatically fixable using the --fix
flag on the command line. However, fix does not include indentation. Please rerun lint to correct those errors.
This rule checks whether the first property of all JSX elements is correctly placed. There are the possible configurations:
always
: The first property should always be placed on a new line.never
: The first property should never be placed on a new line, e.g. should always be on the same line as the Component opening tag.multiline
: The first property should always be placed on a new line when the JSX tag takes up multiple lines.multiline-multiprop
: The first property should always be placed on a new line if the JSX tag takes up multiple lines and there are multiple properties. This is thedefault
value.
The following patterns are considered warnings when configured "always"
:
<Hello personal={true} />
<Hello personal={true}
foo="bar"
/>
The following patterns are not considered warnings when configured "always"
:
<Hello
personal />
<Hello
personal
/>
The following patterns are considered warnings when configured "never"
:
<Hello
personal />
<Hello
personal
/>
The following patterns are not considered warnings when configured "never"
:
<Hello personal={true} />
<Hello personal={true}
foo="bar"
/>
The following patterns are considered warnings when configured "multiline"
:
<Hello personal
prop />
<Hello foo={{
}} />
The following patterns are not considered warnings when configured "multiline"
:
<Hello personal={true} />
<Hello
personal={true}
foo="bar"
/>
The following patterns are considered warnings when configured "multiline-multiprop"
:
<Hello foo={{
}}
bar />
The following patterns are not considered warnings when configured "multiline-multiprop"
:
<Hello foo={{
}} />
<Hello
foo={{
}}
bar
/>
"react/jsx-first-props-per-line": `"always" | "never" | "multiline" | "multiline-multiprop"`
If you are not using JSX then you can disable this rule.