For some reason, / > is valid JSX, as is / followed by any kind of whitespace until the >. This rule would require that the self-closing terminator is always written as an atomic />.
Not having a check for this also allows for funny workarounds for jsx-closing-bracket-location, such as this (when using after-props):
<SomeComponent
with='many'
props='specified' /
>
Update: #693 (comment)
For some reason,
/ >is valid JSX, as is/followed by any kind of whitespace until the>. This rule would require that the self-closing terminator is always written as an atomic/>.Not having a check for this also allows for funny workarounds for jsx-closing-bracket-location, such as this (when using
after-props):Update: #693 (comment)