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
steps to reproduce:
let a = 1 type a = undefined
expected: lints fine
actual:
you couldn't get enough of a, so you had to make two, huh?
While this syntax is confusing, it's frequently used to use const object literals as enums. Like
const
export const Thing = { "A": 1, "B": 2 } as const; type Thing = typeof Thing
quick-lint-js version 2.12.0
The text was updated successfully, but these errors were encountered:
I could take this one.
Sorry, something went wrong.
@leszek888 Sorry, but I am working on this myself.
This has been fixed. I don't know when exactly, but it's working on master and probably quick-lint-js 2.15.0.
No branches or pull requests
steps to reproduce:
expected:
lints fine
actual:
While this syntax is confusing, it's frequently used to use
const
object literals as enums. Likequick-lint-js version 2.12.0
The text was updated successfully, but these errors were encountered: