You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The template compiler behavior changed for the following case:
<template>
<custom-component />
</template>
With Vue 2 this would always resolve custom-component via component registration. With Vue 3, if this file is named CustomComponent.vue (camel-cased version of the tag name) this is automatically considered a self-reference, regardless of the component registration. While this behavior is intentional judging from the source code, it actually caused an infinite recursion in my code because of an unintended self-reference. So it needs to be documented in “Migration from Vue 2” at the very least.
The template compiler behavior changed for the following case:
With Vue 2 this would always resolve
custom-component
via component registration. With Vue 3, if this file is namedCustomComponent.vue
(camel-cased version of the tag name) this is automatically considered a self-reference, regardless of the component registration. While this behavior is intentional judging from the source code, it actually caused an infinite recursion in my code because of an unintended self-reference. So it needs to be documented in “Migration from Vue 2” at the very least.For reference, the relevant commit: vuejs/core@67d1aac
The text was updated successfully, but these errors were encountered: