docs(components): Add info about extensions and pathPrefix keys
#8930
Conversation
|
|
✅ Deploy Preview for nuxt3-docs ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
|
@danielroe I wrote a docs as promised in nuxt/nuxt#15447 Spelling corrections are welcome, also I'm not sure should I use object form of // This one
components: [
{ path: '...' },
],
// or this one
components: {
dirs: [
{ path: '...' },
]
} |
Occurred since was editing via Github interface
| }); | ||
| ``` | ||
|
|
||
| This registers the components using the same strategy as used in Nuxt 2. |
There was a problem hiding this comment.
I think you should explain this more clearly cause not every Nuxt 3 devs have used Nuxt 2.
There was a problem hiding this comment.
I think this is explained well in a paragraph before code block.
The reason I mention Nuxt 2 is this comment (and some next ones).
If developer used Nuxt2 then he will understand, and if he didn't then he has nothing to compare with anyway.
Perhaps this mention is simply redudant, especially if there is a focus on new members of the community.
There was a problem hiding this comment.
I think this is explained well in a paragraph before code block. The reason I mention Nuxt 2 is this comment (and some next ones).
If developer used Nuxt2 then he will understand, and if he didn't then he has nothing to compare with anyway. Perhaps this mention is simply redudant, especially if there is a focus on new members of the community.
I understand your reason, but imo we should explain it since maybe it's the feature that someone have been looking for. Maybe at least an example t ocompar the difference between pathPrefix: false and pathPrefix: true?
|
merged in 28a2a91. |
🔗 Linked issue
nuxt/nuxt#15447 (closed but there were a comments with explanations)
❓ Type of change
📚 Description
Documentation for
extensionsandpathPrefixkeys ofcomponents > dirsobjects ofnuxt.config.ts📝 Checklist