9571ede84b
BREAKING CHANGE: `watch` behavior has been adjusted. - When using the `watch(source, callback, options?)` signature, the callback now fires lazily by default (consistent with 2.x behavior). Note that the `watch(effect, options?)` signature is still eager, since it must invoke the `effect` immediately to collect dependencies. - The `lazy` option has been replaced by the opposite `immediate` option, which defaults to `false`. (It's ignored when using the effect signature) - Due to the above changes, the `watch` option in Options API now behaves exactly the same as 2.x. - When using the effect signature or `{ immediate: true }`, the intital execution is now performed synchronously instead of deferred until the component is mounted. This is necessary for certain use cases to work properly with `async setup()` and Suspense. The side effect of this is the immediate watcher invocation will no longer have access to the mounted DOM. However, the watcher can be initiated inside `onMounted` to retain previous behavior. |
||
---|---|---|
.. | ||
components | ||
helpers | ||
apiCreateApp.spec.ts | ||
apiInject.spec.ts | ||
apiLifecycle.spec.ts | ||
apiOptions.spec.ts | ||
apiSetupContext.spec.ts | ||
apiTemplateRef.spec.ts | ||
apiWatch.spec.ts | ||
component.spec.ts | ||
componentProxy.spec.ts | ||
directives.spec.ts | ||
errorHandling.spec.ts | ||
h.spec.ts | ||
hmr.spec.ts | ||
rendererAttrsFallthrough.spec.ts | ||
rendererChildren.spec.ts | ||
rendererElement.spec.ts | ||
rendererFragment.spec.ts | ||
rendererOptimizedMode.spec.ts | ||
scheduler.spec.ts | ||
vnode.spec.ts |