feat(runtime-vapor): add support for v-once#13459
Conversation
✅ Deploy Preview for vapor-repl ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the ✨ Finishing touches🧪 Generate unit tests (beta)
Comment |
@vue/compiler-core
@vue/compiler-dom
@vue/compiler-sfc
@vue/compiler-ssr
@vue/compiler-vapor
@vue/reactivity
@vue/runtime-core
@vue/runtime-dom
@vue/runtime-vapor
@vue/server-renderer
@vue/shared
vue
@vue/compat
commit: |
Size ReportBundles
Usages
|
| const setFn = () => | ||
| setDynamicProps(el, [resolveDynamicProps(rawProps as RawProps)]) | ||
| }) | ||
| if (once) setFn() |
There was a problem hiding this comment.
Are all of the other side effects of renderEffect safe/desired to avoid in the event of a v-once e.g. setCurrentInstance, beforeUpdate/updated lifecycle hooks, startMeasure in RenderEffect.fn()?
There was a problem hiding this comment.
The renderEffect inside the component remains unchanged. I believe what v-once aims to achieve is to prevent component updates caused by changes in props/attrs
No description provided.