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
{{ message }}
This repository has been archived by the owner on Mar 25, 2021. It is now read-only.
This bug is actually creating crazy issues in VSCode where you have to basically disable the whitepsace check, otherwise it throws random errors for lines all in the incorrect locations etc.
I haven't seen this rule throw "random errors", but a related case I have seen is when using for (;;) to make an infinite loop (without triggering strict-boolean-expressions). TSLint warns about this code:
Which seems unnecessary to me. My recommendation is to make an exception for the "check-separator" case when the following element is empty/absent. That should cover both cases. It would also allow something like const [a,, b] = ignoreMiddleReturn() - I'm not sure if that's problematic.
Bug Report
4.5.1
2.2.1
TypeScript code being linted
with
tslint.json
configuration:Actual behavior
Emit error:
Expected behavior
No error.
The text was updated successfully, but these errors were encountered: