-
-
Notifications
You must be signed in to change notification settings - Fork 442
pug v-if not guarded as defined / != null #2329
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
Comments
It can be |
@rchl |
That's true, the element will disappear then. I suppose that's not something the type system is aware of though so it might be hard to fix, if possible at all. Also there might be an issue like that already. |
As far as I know in a much historical previous version of volar this was working and didn't complain |
We used to support it in 0.21.6, then removed it in 0.21.14, so it caused some wrong type behavior. |
@johnsoncodehk I hope I just did not missed it but I feel like you need to setup a documentation (Maybe even with VitePress like other Vue-Ecosystem tools) |
Yes we plan to document it at https://vuejs.org/. |
Good idea. :) |
@johnsoncodehk I see in my tsconfig when setting this value that |
I have a weird bug 🤔
I have a component and use
v-if="panel"
for checking if the variable is notnull
But in the
@click
it is still nullable, but this will never benull
thereThe text was updated successfully, but these errors were encountered: