-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
feat(nuxt): generate basic jsdoc for module config entry #27689
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
Conversation
|
Currently the information we have are kinda limited: Should we encourage module authors to have more fields in meta, like nuxt/packages/schema/src/types/module.ts Lines 5 to 24 in 1949231
/cc @pi0 @danielroe |
Thank you for working on it ❤️ I like the |
Maybe we could add the jsdoc tags to only one of the augmented modules? |
It should be good now; I assume |
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.
Lovely - thank you! ❤️
It's possible there are still some edge cases (like alternative registries) but we can always iterate if needed.
Before:
After:
The duplication of tags are because we are extending both
@nuxt/schema
andnuxt/schema
- I guess it won't hurt much, we could figure out it later, or we only generate jsdoc for one of them?