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
Note that this is not a real bug, just an optimization item.
see Playground
It seems no need to wrap it as an IIFE.
setup(__props) { const msg = ref('Hello World!') return ((_ctx) => { const n0 = t0() _setInheritAttrs(false) _renderEffect(() => _setText(n0, msg.value)) return n0 })() }
better is:
setup(__props) { const msg = ref('Hello World!') const n0 = t0() _setInheritAttrs(false) _renderEffect(() => _setText(n0, msg.value)) return n0 }
The text was updated successfully, but these errors were encountered:
Instead of msg, it could be anything, including n0, which is why there's an IIFE
msg
n0
Sorry, something went wrong.
We can use Block Statement Or use compiler static analysis to adapted generation result
No branches or pull requests
Note that this is not a real bug, just an optimization item.
see Playground
It seems no need to wrap it as an IIFE.
better is:
The text was updated successfully, but these errors were encountered: