Closed urbanhusky closed 3 years ago
Thank you for the report, @urbanhusky. Will look into it this weekend
Fixed in v0.7.1
Seems to work fine now, thanks.
I did have to change the rule overwrites from 'no-unused-expressions': 'off',
to '@typescript-eslint/no-unused-expressions': 'off',
to get it to work again though :)
When using
chai-friendly/no-unused-expressions
instead of the defaultno-unused-expressions
, all code with optional chaining operators seems to fail with ESLint: Expected an assignment or function call and instead saw an expression. (@typescript-eslint/no-unused-expressions)For example:
This renders the plugin unusable for me and I'm not sure if I could trust it to otherwise operate the same way and provide the same confidence in our code as eslint's
no-unused-expressions
.