We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
vue/no-ref-as-operand
Ref | NotARef
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
Checklist
Tell us about your environment
Please show your full configuration:
module.exports = { extends: ['jkarczm/vuetify'], parserOptions: { project: 'tsconfig.json', }, }
(where jkarczm/vuetify is from https://github.com/jacekkarczmarczyk/eslint-config-jkarczm package, but probably including only vue/no-ref-as-operand matters)
jkarczm/vuetify
What did you do?
let foo: Ref<number> | undefined; if (!foo) { foo = ref(5); }
What did you expect to happen?
no error, no autofixing
What actually happened?
code was "fixed" to
let foo: Ref<number> | undefined; if (!foo.value) { foo.value = ref(5); }
The text was updated successfully, but these errors were encountered:
let foo; foo = Reactive(bar)
triggers the same bug.
Sorry, something went wrong.
This was caused by #1965 I think, because those cases didn't trigger an error before and they now do
Successfully merging a pull request may close this issue.
Checklist
Tell us about your environment
Please show your full configuration:
(where
jkarczm/vuetify
is from https://github.com/jacekkarczmarczyk/eslint-config-jkarczm package, but probably including onlyvue/no-ref-as-operand
matters)What did you do?
What did you expect to happen?
no error, no autofixing
What actually happened?
code was "fixed" to
The text was updated successfully, but these errors were encountered: