-
-
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
Source: Support async parameters.docs.source.transform #30426
base: next
Are you sure you want to change the base?
Source: Support async parameters.docs.source.transform #30426
Conversation
View your CI Pipeline Execution ↗ for commit 9b88069.
☁️ Nx Cloud last updated this comment at |
Package BenchmarksCommit: No significant changes detected, all good. 👏 |
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.
4 file(s) reviewed, 4 comment(s)
Edit PR Review Bot Settings | Greptile
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.
A few comments.
I also think it deserves a migration note, describing how you can implement the current formatter as an async transfomer.
Probably also needs @shilman's blessing on deprecating docs.source.format
in favor of asking users to implement their own if they want to, probably with prettier.
The rationale is that the current format
feature is half-baked because it only supports a hard-coded limited set of languages, and it requires a hefty prettier bundled in.
const sourceParameters = (storyContext.parameters.docs?.source || {}) as SourceParameters; | ||
const parameters = storyContext.parameters ?? {}; | ||
const { __isArgsStory: isArgsStory } = parameters; | ||
const [transformedCode, setTransformedCode] = useState('Loading...'); |
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.
- Maybe
'Transforming...'
instead of'Loading...'
? - the default could also just be
code
if we detect that there is no transformer, and'Transforming...'
if there is? - The default could also just always be
code
, to be replaced by the transformed code afterwards.
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.
the default could also just be code if we detect that there is no transformer, and 'Transforming...' if there is?
It is a bit of a spaghetti code, but at the bottom of the hook, transformedCode
is not used if code
is defined. I don't prefer to set the default to code
because then you might have a flickering between two codes, and you might not understand why it was changing. Transforming...
indicates that the transformation is still in progress and you should wait to interpret the code. transform
can not just be used to format code, but also to display something completely different (I think we use a very custom transformer for Angular for example).
|
||
Type: `boolean | 'dedent' | BuiltInParserName` | ||
|
||
Default: `parameters.docs.source.format` or `true` | ||
|
||
Deprecated: Will be removed in Storybook 9. Please use `docs.source.transform` instead and use your own formatter |
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.
I think an example of how to do this with prettier here would come a long way.
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.
Agree
Good catches! I'll take care of it. |
Co-authored-by: Kyle Gach <[email protected]>
…-source-transform-async
…-source-transform-async
…-source-transform-async
Closes #24236
Closes #23703
What I did
parameters.docs.source.transform
parameters.docs.source.format
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-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.🦋 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>
Greptile Summary
Added support for asynchronous source code transformation in Storybook's Source Doc Block, allowing dynamic code processing with async functions while deprecating the format parameter.
parameters.docs.source.transform
incode/lib/blocks/src/blocks/Source.tsx
using React hooksAsyncTransform
example incode/addons/docs/template/stories/docspage/source.stories.ts
demonstrating async usageparameters.docs.source.format
parameter in favor of custom transformers indocs/api/doc-blocks/doc-block-source.mdx
code/addons/docs/docs/recipes.md
with async transform examples and migration guidance