-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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: Doc Blocks updates for known limitations #25248
Conversation
docs/api/doc-block-controls.md
Outdated
@@ -31,7 +31,7 @@ import * as ButtonStories from './Button.stories' | |||
|
|||
<Callout variant="warning"> | |||
|
|||
The Controls doc block will only have functioning UI controls if you have also installed and registered [`@storybook/addon-controls`](../essentials/controls.md) (included in [`@storybook/addon-essentials`](../essentials/index.md)). | |||
The Controls doc block will only have functioning UI controls if you have also installed and registered [`@storybook/addon-controls`](../essentials/controls.md) (included in [`@storybook/addon-essentials`](../essentials/index.md)) and haven't turned off inline stories with the [`inlineStories`](./doc-block-story.md#inline) configuration option. |
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.
It's confusing to reference a non-existent property with the code formatting, which makes it seem like it's a real thing. The preceding "inline stories" adds enough clarity, I think.
The Controls doc block will only have functioning UI controls if you have also installed and registered [`@storybook/addon-controls`](../essentials/controls.md) (included in [`@storybook/addon-essentials`](../essentials/index.md)) and haven't turned off inline stories with the [`inlineStories`](./doc-block-story.md#inline) configuration option. | |
The Controls doc block will only have functioning UI controls if you have also installed and registered [`@storybook/addon-controls`](../essentials/controls.md) (included in [`@storybook/addon-essentials`](../essentials/index.md)) and haven't turned off inline stories with the [`inline`](./doc-block-story.md#inline) configuration option. |
docs/api/doc-block-source.md
Outdated
|
||
### `excludeDecorators` | ||
|
||
Type: |
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.
Type: | |
Type: `boolean` |
docs/writing-docs/autodocs.md
Outdated
@@ -286,6 +286,10 @@ Additionally, if you're developing using TypeScript, you may need to update Stor | |||
|
|||
If you're still encountering issues, we recommend reaching out to the community using the default communication channels (e.g., [GitHub discussions](https://github.com/storybookjs/storybook/discussions/new?category=help)). | |||
|
|||
### The controls are not updating the story within the auto-generated documentation | |||
|
|||
If you turned off inline rendering for your stories via the [`inlineStories`](../api/doc-block-story.md) configuration option, you would run into a situation where the associated controls are not updating the story within the documentation page. This is a known limitation of the current implementation and will be addressed in a future release. |
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.
If you turned off inline rendering for your stories via the [`inlineStories`](../api/doc-block-story.md) configuration option, you would run into a situation where the associated controls are not updating the story within the documentation page. This is a known limitation of the current implementation and will be addressed in a future release. | |
If you turned off inline rendering for your stories via the [`inline`](../api/doc-block-story.md) configuration option, you would run into a situation where the associated controls are not updating the story within the documentation page. This is a known limitation of the current implementation and will be addressed in a future release. |
docs/writing-docs/mdx.md
Outdated
@@ -455,6 +455,10 @@ Additionally, if you're working with VSCode, you can add the [MDX extension](htt | |||
|
|||
If you're still encountering issues, we recommend reaching out to the community using the default communication channels (e.g., [GitHub discussions](https://github.com/storybookjs/storybook/discussions/new?category=help)). | |||
|
|||
### The controls are not updating the story within the MDX documentation page | |||
|
|||
If you turned off inline rendering for your stories via the [`inlineStories`](../api/doc-block-story.md) configuration option, you would run into a situation where the associated controls are not updating the story within the documentation page. This is a known limitation of the current implementation and will be addressed in a future release. |
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.
If you turned off inline rendering for your stories via the [`inlineStories`](../api/doc-block-story.md) configuration option, you would run into a situation where the associated controls are not updating the story within the documentation page. This is a known limitation of the current implementation and will be addressed in a future release. | |
If you turned off inline rendering for your stories via the [`inline`](../api/doc-block-story.md) configuration option, you would run into a situation where the associated controls are not updating the story within the documentation page. This is a known limitation of the current implementation and will be addressed in a future release. |
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.
Good updates! Made a few suggestions, but they're easy to incorporate, so I'm going to go ahead and approve to un-block you.
Docs: Doc Blocks updates for known limitations (cherry picked from commit 76340fc)
Docs: Doc Blocks updates for known limitations (cherry picked from commit 76340fc)
Docs: Doc Blocks updates for known limitations (cherry picked from commit 76340fc)
Docs: Doc Blocks updates for known limitations (cherry picked from commit 76340fc)
Docs: Doc Blocks updates for known limitations (cherry picked from commit 76340fc)
Docs: Doc Blocks updates for known limitations (cherry picked from commit 76340fc)
Docs: Doc Blocks updates for known limitations (cherry picked from commit 76340fc)
Docs: Doc Blocks updates for known limitations (cherry picked from commit 76340fc)
Closes #24267 and closes #22267
What I did
With this small pull request the relevant sections were updated to reflect some of the gaps and limitations of generating documentation with Storybook.
@JReinhold, when you have a moment, can you take a look and let me know of any feedback you may have so that we can close out the associated issues? Thanks in advance.
Checklist for Contributors
Testing
The changes in this PR are covered in the following automated tests:
Manual testing
This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!
Documentation
MIGRATION.MD
Checklist for Maintainers
When this PR is ready for testing, make sure to add
ci:normal
,ci:merged
orci:daily
GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found incode/lib/cli/src/sandbox-templates.ts
Make sure this PR contains one of the labels below:
Available labels
bug
: Internal changes that fixes incorrect behavior.maintenance
: User-facing maintenance tasks.dependencies
: Upgrading (sometimes downgrading) dependencies.build
: Internal-facing build tooling & test updates. Will not show up in release changelog.cleanup
: Minor cleanup style change. Will not show up in release changelog.documentation
: Documentation only changes. Will not show up in release changelog.feature request
: Introducing a new feature.BREAKING CHANGE
: Changes that break compatibility in some way with current major version.other
: Changes that don't fit in the above categories.🦋 Canary release
This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the
@storybookjs/core
team here.core team members can create a canary release here or locally with
gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=<PR_NUMBER>