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
Linux
v16.12.0
3.0.0-rc.11
0.5.4
yarn@1.22.19
vite
alias
content
nitro
modules
extends
github
colorMode
runtimeConfig
@nuxtjs/algolia@1.1.4
-
index.md:
::something #truevar This is true! Hello! #falsevar This is false! :(
Something.vue:
<template> <div v-if="test"> <slot name="truevar"></slot> </div> <div v-if="!test"> <slot name="falsevar"></slot> </div> </template> <script setup> const test = ref(true) setInterval(()=>{ test.value = !test.value }, 1000) </script>
In the real world, of course, I use useState instead of setInterval, but the action is the same.
When there is a component in a file, e.g. .md, which has component with a v-if and this v-if changes its state frequently then <slot> disappears.
<slot>
No response
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Environment
Linux
v16.12.0
3.0.0-rc.11
0.5.4
yarn@1.22.19
vite
alias
,content
,nitro
,modules
,extends
,github
,colorMode
,runtimeConfig
@nuxtjs/algolia@1.1.4
-
Reproduction
index.md:
Something.vue:
In the real world, of course, I use useState instead of setInterval, but the action is the same.
Describe the bug
When there is a component in a file, e.g. .md, which has component with a v-if and this v-if changes its state frequently then
<slot>
disappears.Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: