New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[no-unused-expressions] False positive with optional chaining #1138
Closed
ipcjs opened this issue
Oct 25, 2019
· 3 comments
· Fixed by #1175 or kaliber5/k5-ember-boilerplate#3
Closed
[no-unused-expressions] False positive with optional chaining #1138
ipcjs opened this issue
Oct 25, 2019
· 3 comments
· Fixed by #1175 or kaliber5/k5-ember-boilerplate#3
Labels
bug
Something isn't working
has pr
there is a PR raised to close this
package: eslint-plugin
Issues related to @typescript-eslint/eslint-plugin
Comments
ipcjs
added
package: eslint-plugin
Issues related to @typescript-eslint/eslint-plugin
triage
Waiting for maintainers to take a look
labels
Oct 25, 2019
bradzacher
added
bug
Something isn't working
scope analyser
Issues that are caused by bugs/incomplete cases in the scope analyser
and removed
triage
Waiting for maintainers to take a look
labels
Oct 25, 2019
Same root cause as #1090 et al |
This was referenced Oct 26, 2019
bradzacher
added
has pr
there is a PR raised to close this
and removed
scope analyser
Issues that are caused by bugs/incomplete cases in the scope analyser
labels
Nov 8, 2019
Is this problem solved? Versions:
|
please don't comment on closed issues. |
lolmaus
pushed a commit
to kaliber5/k5-ember-boilerplate
that referenced
this issue
Mar 10, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bug
Something isn't working
has pr
there is a PR raised to close this
package: eslint-plugin
Issues related to @typescript-eslint/eslint-plugin
Repro
Expected Result
Actual Result
Versions
@typescript-eslint/eslint-plugin
2.5.0
@typescript-eslint/parser
2.5.0
TypeScript
3.7.0-dev.20191021
ESLint
5.16.0
node
v10.15.3
npm
6.10.1
The text was updated successfully, but these errors were encountered: