You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We had a case in our code where a semicolon was accidentally used at the end of a line of a tsx statement. Since this is almost always unintended, it makes sense to have a lint rule to warn against it. The rule would warn against code like the following:
<div>
<SomeComponent/>;
</div>
(haven't thought about the rule name that much, so take the title with a grain of salt)
The text was updated successfully, but these errors were encountered:
I was just looking for something like this. Maybe no-errant-characters? Is there an actual use-case for having characters not wrapped in an element in a JSX statement? For RN there is not.
We had a case in our code where a semicolon was accidentally used at the end of a line of a tsx statement. Since this is almost always unintended, it makes sense to have a lint rule to warn against it. The rule would warn against code like the following:
(haven't thought about the rule name that much, so take the title with a grain of salt)
The text was updated successfully, but these errors were encountered: