Skip to content
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

[Documentation]: using children as an arg section missing completely from docs #27179

Open
tbredin opened this issue May 17, 2024 · 1 comment

Comments

@tbredin
Copy link

tbredin commented May 17, 2024

Describe the problem

https://storybook.js.org/docs/writing-stories/stories-for-multiple-components#using-children-as-an-arg

This section still shows up in google, and the sidebar menu item still exists, but it links nowhere and there appears to be a missing section in the docs on this page, and elsewhere seems not to be any documentation about using the children arg on the site anymore. As a result, I must be using it wrong because it just throws errors for me, and I can't work out how to get it to work or how its intended to be used.

  1. If this feature was removed in v8 or something like this, perhaps a depreciation message would be suitable in the docs so that we don't chase a no longer supported feature, and providing an alternative encouraged approach would be appreciated
  2. If it is still supported then we need some documentation

Thanks!

Additional context

No response

@jonniebigodes
Copy link
Contributor

@tbredin thanks for taking the time to reach out to us with your question. We appreciate it 🙏 ! So that you're aware the documentation exists, but is framework specific (i.e., React), if you happen to switch to another supported framework, then the relevant section is not shown as shown in the recording below.

conditional-docs.mp4

However, regarding it showing up in the sidebar, this is a known issue that we're aiming to solve soon, so that you and any other users don't run into this type of scenario as well.

Additionally, regarding the google indexing, I have to check, but I believe it's probably indexing a specific framework which can yield this type of issue once again.

Looking forward to hearing from you.

Hope you have a great day

Stay safe

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

3 participants