WIP: Angular: Fix csf-plugin usage#24660
Closed
valentinpalkovic wants to merge 1 commit into
Closed
Conversation
valentinpalkovic
added
ci:daily
|
New dependencies detected. Learn more about Socket for GitHub ↗︎
|
valentinpalkovic
force-pushed
the
valentin/fix-csf-loader-for-angular
branch
3 times, most recently
from
0299a35 to
1b7a9fe
Compare
shilman
reviewed
Nov 2, 2023
| }, | ||
| "dependencies": { | ||
| "@storybook/csf-tools": "workspace:*", | ||
| "unplugin": "^1.3.1" |
| } | ||
|
|
||
| export const loadCsf = (code: string, options: CsfOptions) => { | ||
| export const loadCsf = (code: string, originalCode: string, options: CsfOptions) => { |
Member
There was a problem hiding this comment.
if this is necessary, can we please make originalCode an optional field on the options object? this is a very disruptive PR otherwise, and loadCsf is also used in other packages outside of the monorepo
shilman
reviewed
Nov 2, 2023
| /** @deprecated */ | ||
| sourceLoaderOptions: any; | ||
| csfPluginOptions: CsfPluginOptions | null; | ||
| csfPluginOptions: CsfOptions | null; |
Member
There was a problem hiding this comment.
what's the point of this breaking change?
valentinpalkovic
changed the title
valentinpalkovic
force-pushed
the
valentin/fix-csf-loader-for-angular
branch
from
1b7a9fe to
4274760
Compare
8 tasks
valentinpalkovic
force-pushed
the
valentin/fix-csf-loader-for-angular
branch
from
4274760 to
e28774c
Compare
Contributor
Author
|
Superseded by #25098 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #21387, #17233, #24241, #20475, #14043
What I did
TBD
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:mergedorci:dailyGH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found incode/lib/cli/src/sandbox-templates.tsMake 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/coreteam 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>