-
-
Notifications
You must be signed in to change notification settings - Fork 657
New issue
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
docs(migration): state how to register components in content
folder as global components
#2935
docs(migration): state how to register components in content
folder as global components
#2935
Conversation
β¦ as global components In v2, this was done automatically. It has to be explicitly added in v3.
Aside from hook, the file names can be renamed to include |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR. However, this action is not necessary for all users, in your case it is required because you are using these components as dynamic components.
Instead of adding a section, let's add a note in Rendering Components
section and notify about changing from global to non-global. And link to Nuxt Custom Components Directories for more details about Nuxt components system.
Yes. You can do that too. For me, there are too many global components to do this. |
β¦he `Render Components` section
I made the changes just now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
Beautifull work |
In v2, this was done automatically. It has to be explicitly added in v3.
The issue raised can be found here #2930
π Linked issue
β Type of change
π Description
While migrating from v2, I noticed that all the components that were once global and could be passed as a string to the
<component />
element were no longer being displayed. The components created undercomponents/content
were no longer automatically registered as global components.This PR just adds this note to the migration page so that users know that they have to explicitly mark components within the
components/content
folder as global.π Checklist