Skip to content

FastBuild: Improve config loading & naming#24837

Merged
ndelangen merged 2 commits intonextfrom
norbert/fix-testbuildflags
Nov 14, 2023
Merged

FastBuild: Improve config loading & naming#24837
ndelangen merged 2 commits intonextfrom
norbert/fix-testbuildflags

Conversation

@ndelangen
Copy link
Member

What I did

  • rename the properties on the TestBuild interface
  • ensure the default values get added instead of dropped when users specify overrides

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>

Copy link
Contributor

@kasperpeulen kasperpeulen left a comment

Choose a reason for hiding this comment

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

Nice!

Copy link
Member

@shilman shilman left a comment

Choose a reason for hiding this comment

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

Great stuff!!! 🙌

@ndelangen ndelangen merged commit 9ad493f into next Nov 14, 2023
@ndelangen ndelangen deleted the norbert/fix-testbuildflags branch November 14, 2023 13:25
@github-actions github-actions bot mentioned this pull request Nov 14, 2023
8 tasks
return (
!name.includes('@storybook/addon-docs') && !name.includes('@storybook/addon-coverage')
);
return !!storybookOptions.build?.test?.disabledAddons?.find((n) => name.includes(n));
Copy link
Member

@IanVS IanVS Nov 20, 2023

Choose a reason for hiding this comment

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

@ndelangen I think the logic here is backwards. Instead of filtering out disabled addons, it only allows disabled addons, since there is a double bang. I found that my storybook started breaking in alpha.6 unless I provided an explicit disabledAddons: []. Even just disabledAddons: ['foo'] broke it, which I think is because it causes this code to execute.

Copy link
Member Author

Choose a reason for hiding this comment

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

😱 I'll fix it

@IanVS IanVS mentioned this pull request Nov 20, 2023
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants