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

Docs: Doc Blocks updates for known limitations #25248

Merged
merged 8 commits into from
Dec 22, 2023

Conversation

jonniebigodes
Copy link
Contributor

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:

  • stories
  • unit tests
  • integration tests
  • end-to-end tests

Manual testing

This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!

Documentation

  • Add or update documentation reflecting your changes
  • If you are deprecating/removing a feature, make sure to update
    MIGRATION.MD

Checklist for Maintainers

  • When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/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>

@jonniebigodes jonniebigodes added documentation patch:yes Bugfix & documentation PR that need to be picked to main branch ci:docs Run the CI jobs for documentation checks only. labels Dec 15, 2023
@jonniebigodes jonniebigodes self-assigned this Dec 15, 2023
@jonniebigodes jonniebigodes changed the title Docs: Documentation updates for known limitations Docs: Doc Blocks updates for known limitations Dec 18, 2023
@@ -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.
Copy link
Contributor

@kylegach kylegach Dec 18, 2023

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.

Suggested change
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.


### `excludeDecorators`

Type:
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
Type:
Type: `boolean`

@@ -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.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
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.

@@ -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.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
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.

Copy link
Contributor

@kylegach kylegach left a 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.

@jonniebigodes jonniebigodes merged commit 76340fc into next Dec 22, 2023
18 checks passed
@jonniebigodes jonniebigodes deleted the docs_fix_doc_blocks_apis branch December 22, 2023 13:00
storybook-bot pushed a commit that referenced this pull request Dec 22, 2023
Docs: Doc Blocks  updates for known limitations
(cherry picked from commit 76340fc)
storybook-bot pushed a commit that referenced this pull request Dec 22, 2023
Docs: Doc Blocks  updates for known limitations
(cherry picked from commit 76340fc)
storybook-bot pushed a commit that referenced this pull request Dec 22, 2023
Docs: Doc Blocks  updates for known limitations
(cherry picked from commit 76340fc)
storybook-bot pushed a commit that referenced this pull request Dec 24, 2023
Docs: Doc Blocks  updates for known limitations
(cherry picked from commit 76340fc)
storybook-bot pushed a commit that referenced this pull request Dec 28, 2023
Docs: Doc Blocks  updates for known limitations
(cherry picked from commit 76340fc)
storybook-bot pushed a commit that referenced this pull request Dec 29, 2023
Docs: Doc Blocks  updates for known limitations
(cherry picked from commit 76340fc)
storybook-bot pushed a commit that referenced this pull request Dec 29, 2023
Docs: Doc Blocks  updates for known limitations
(cherry picked from commit 76340fc)
storybook-bot pushed a commit that referenced this pull request Dec 29, 2023
Docs: Doc Blocks  updates for known limitations
(cherry picked from commit 76340fc)
@github-actions github-actions bot added the patch:done Patch/release PRs already cherry-picked to main/release branch label Jan 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci:docs Run the CI jobs for documentation checks only. documentation patch:done Patch/release PRs already cherry-picked to main/release branch patch:yes Bugfix & documentation PR that need to be picked to main branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Documentation]: excludeDecorators property missing in docs Clarify limitations of <Story inline={false} />
3 participants