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: Add CSF factory API documentation #30343

Open
wants to merge 5 commits into
base: kasper/csf-factories
Choose a base branch
from

Conversation

yannbf
Copy link
Member

@yannbf yannbf commented Jan 22, 2025

Closes #30342
Closes #30329

What I did

This PR introduces documentation for the CSF Factory format.

Checklist for Contributors

Testing

Manual testing

  1. Check out this branch
  2. Run sync-docs in storybookjs/web locally
  3. Run the docs site locally
    • Make sure you've pulled the latest main, so the page-level tabs show up
  4. Visit http://localhost:3000/docs/api/csf/csf-factories

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-storybook/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.

Greptile Summary

This PR introduces comprehensive documentation for the new CSF Factory API, providing examples and guidelines for creating and testing Storybook stories with improved type safety and reusability.

  • Added new defineMain and definePreview configuration examples in docs/_snippets/csf-factories-main-example.md and docs/_snippets/csf-factories-preview-example.md
  • Added story creation examples using preview.meta() and meta.story() in docs/_snippets/csf-factories-story-example.md
  • Added testing integration examples with Vitest in docs/_snippets/portable-stories-csf-factory-run.md
  • Updated portable stories documentation with warnings about CSF Factory API preference for React users
  • Added documentation for story composition and property reuse through the composed property

@yannbf yannbf added the ci:docs Run the CI jobs for documentation checks only. label Jan 22, 2025
@yannbf yannbf self-assigned this Jan 22, 2025
Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

10 file(s) reviewed, 12 comment(s)
Edit PR Review Bot Settings | Greptile

const Secondary = meta.story({
args: {
// 👇 Access args from another story using its `composed` property
...Primary.composed.args,
Copy link
Contributor

Choose a reason for hiding this comment

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

logic: spreading Primary.composed.args and then overriding label with the same value ('Button') appears redundant since it's the same as the Primary story

Comment on lines 10 to 14
const Primary = meta.story({
args: {
label: 'Button',
},
});
Copy link
Contributor

Choose a reason for hiding this comment

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

style: consider adding export statements to make these stories available to Storybook

Comment on lines 10 to 14
const Primary = meta.story({
args: {
label: 'Button',
},
});
Copy link
Contributor

Choose a reason for hiding this comment

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

logic: Primary story should be exported to be visible in Storybook

docs/_snippets/portable-stories-csf-factory-render.md Outdated Show resolved Hide resolved
docs/_snippets/portable-stories-csf-factory-run.md Outdated Show resolved Hide resolved
docs/api/csf.mdx Outdated
import preview from '../../../.storybook/preview';
```

For more details, refer to the [subpath imports documentation](../writing-stories/mocking-modules#subpath-imports).
Copy link
Contributor

Choose a reason for hiding this comment

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

syntax: The link to subpath imports documentation is incorrect. The URL should be ../writing-stories/mocking-modules.mdx#subpath-imports (missing .mdx extension)

Comment on lines 21 to 23
<Callout variant="warning">
If you are using the CSF Factory format, you don't need to use the portable stories API. Instead, you can use the [CSF Factory API](../../api/csf.mdx).
</Callout>
Copy link
Contributor

Choose a reason for hiding this comment

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

style: link to CSF Factory API should be more specific - consider linking directly to the CSF Factory section of the CSF documentation

Copy link

nx-cloud bot commented Jan 22, 2025

View your CI Pipeline Execution ↗ for commit 6e6eb53.

Command Status Duration Result
nx run-many -t build --parallel=3 ✅ Succeeded 1m 50s View ↗

☁️ Nx Cloud last updated this comment at 2025-02-05 18:02:26 UTC

Comment on lines +149 to +152
"#.storybook/preview": {
"default": "./.storybook/preview.ts",
},
"#*": ["./*", "./*.ts", "./*.tsx"],
Copy link
Member Author

Choose a reason for hiding this comment

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

Interesting 🤔 the codemod only adds "#*": ["./*", "./*.ts", "./*.tsx"] and assumes that users will write #.storybook/preview which will relate to <root>.storybook/preview and if they have the preview file somewhere else, they will have to adjust the import in each file to something like #some-dir/.storybook/preview.

This means users with multiple Storybooks could have multiple imports like #apps/.storybook/preview and #libs/.storybook/preview without having to change anything in their package.json.

Perhaps the codemod should set this more specific field like what Kyle wrote here instead? WDYT @kasperpeulen?

Copy link
Contributor

Choose a reason for hiding this comment

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

I see! Thanks for explaining. That's tricky. I see why you did it the current way, but think the way I documented is perhaps a bit more informative? I like that if someone does a Find for #.storybook/preview, they'll come across this.

Copy link
Member Author

Choose a reason for hiding this comment

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

It's tricky, I'll leave @kasperpeulen to decide

Copy link
Contributor

Choose a reason for hiding this comment

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

@kasperpeulen — Did you have thoughts? I'm still inclined to think it should be the way I've documented here, because:

I like that if someone does a Find for #.storybook/preview, they'll come across this.

Copy link
Contributor

Choose a reason for hiding this comment

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

I'm not sure, I will let @shilman decide about this. :P

@kylegach kylegach force-pushed the yann/csf-factories-documentation branch from 5f60838 to e6e01c1 Compare February 4, 2025 22:01
@kylegach kylegach force-pushed the yann/csf-factories-documentation branch from e6e01c1 to dcfab08 Compare February 4, 2025 22:02
@yannbf
Copy link
Member Author

yannbf commented Feb 5, 2025

@kylegach this all looks great, thanks for working on the revisions! I can't approve since I opened the PR, so please approve it for me!

@yannbf yannbf mentioned this pull request Feb 5, 2025
8 tasks
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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants