Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

trdln
Copy link
Contributor

@trdln trdln commented Mar 1, 2024

πŸ”— Linked issue

No issue, just a minor addition to the documentation.

❓ Type of change

  • πŸ“– Documentation (updates to the documentation, readme or JSdoc annotations)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • πŸ‘Œ Enhancement (improving an existing functionality like performance)
  • ✨ New feature (a non-breaking change that adds functionality)
  • 🧹 Chore (updates to the build process or auxiliary tools and libraries)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

πŸ“š Description

Added information about <DevOnly> component in Api section of docs. Information about component was only in Guide section.

πŸ“ Checklist

  • I have linked an issue or discussion.
  • I have added tests (if possible).
  • I have updated the documentation accordingly.

Copy link

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

Copy link
Contributor

nuxt-studio bot commented Mar 1, 2024

βœ… Live Preview ready!

Name Edit Preview Latest Commit
Nuxt Docs Edit on Studio β†—οΈŽ View Live Preview c65b083

Copy link
Member

@danielroe danielroe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@trdln
Copy link
Contributor Author

trdln commented Mar 3, 2024

Seems fine for me, at your discretion.

@danielroe
Copy link
Member

Then yes, let's do it.

@trdln
Copy link
Contributor Author

trdln commented Mar 5, 2024

Should we remove <ClientOnly> and <NuxtClientFallback> components too from https://nuxt.com/docs/guide/directory-structure/components?

@danielroe
Copy link
Member

danielroe commented Mar 5, 2024

That would make sense to me, as long as we have links and ensure the content is still present in the docs on the pages about those specific components. wdyt @atinux?

@atinux
Copy link
Member

atinux commented Mar 5, 2024

Good for me to move them to the API, I still believe that it is nice to have a small section in the components directory page to mention about those DevOnly and ClientOnly components and link to them on the API section

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants