We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As reported in mgechev/codelyzer#859, #205 (comment) and #269 (comment), column numbers are off by one.
Sample:
angular-eslint/packages/eslint-plugin-template/tests/rules/no-call-expression.test.ts
Lines 44 to 45 in b7ea86c
I noticed that we have a hacky way to handle this in no-negated-async:
no-negated-async
angular-eslint/packages/eslint-plugin-template/src/rules/no-negated-async.ts
Line 40 in c8dd14c
Lines 57 to 58 in c8dd14c
The text was updated successfully, but these errors were encountered:
This is related to #292
If you turn on preserveWhitespaces, this off-by-one is resolved.
Sorry, something went wrong.
I'll migrate @rafaelss95 comment to that issue, I have reported it to the Angular tooling team and asked for a process
No branches or pull requests
As reported in mgechev/codelyzer#859, #205 (comment) and #269 (comment), column numbers are off by one.
Sample:
angular-eslint/packages/eslint-plugin-template/tests/rules/no-call-expression.test.ts
Lines 44 to 45 in b7ea86c
I noticed that we have a hacky way to handle this in
no-negated-async
:angular-eslint/packages/eslint-plugin-template/src/rules/no-negated-async.ts
Line 40 in c8dd14c
angular-eslint/packages/eslint-plugin-template/src/rules/no-negated-async.ts
Lines 57 to 58 in c8dd14c
The text was updated successfully, but these errors were encountered: