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

Build: Add sandbox for react-16 #25199

Merged
merged 9 commits into from
Dec 18, 2023
Merged

Conversation

ndelangen
Copy link
Member

@ndelangen ndelangen commented Dec 12, 2023

Telescoped #25196

Works on #25179

What I did

Add a sandbox for testing with react16

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>

@ndelangen ndelangen changed the title add sandbox for react16 Build: Add sandbox for react-16 Dec 12, 2023
@ndelangen ndelangen self-assigned this Dec 12, 2023
@ndelangen ndelangen added build Internal-facing build tooling & test updates ci:normal labels Dec 12, 2023
@ndelangen ndelangen added ci:daily Run the CI jobs that normally run in the daily job. and removed ci:normal labels Dec 12, 2023
@@ -641,6 +654,7 @@ export const daily: TemplateKey[] = [
'preact-webpack5/default-js',
'preact-vite/default-js',
'html-vite/default-js',
'internal/react16-webpack',
Copy link
Member Author

Choose a reason for hiding this comment

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

This should do it right?

I ran yarn get-template --cadence daily --check but it didn't prompt me to change any numbers, which i was expecting.

Copy link
Contributor

Choose a reason for hiding this comment

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

It's because the template has inDevelopment: true, it gets completely ignored. you need to remove that flag and then to the dance:

  1. Changing the sandbox generator to point at this branch
  2. Trigger the generator
  3. Change the sandbox generator back again
  4. Merge this before the daily generator kicks in

Copy link
Member

Choose a reason for hiding this comment

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

This is what should have happened without the inDevelopment flag:
image

I added a small note to the generated message which will show the inDev templates, hopefully will make things less confusing!

@@ -641,6 +654,7 @@ export const daily: TemplateKey[] = [
'preact-webpack5/default-js',
'preact-vite/default-js',
'html-vite/default-js',
'internal/react16-webpack',
Copy link
Contributor

Choose a reason for hiding this comment

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

It's because the template has inDevelopment: true, it gets completely ignored. you need to remove that flag and then to the dance:

  1. Changing the sandbox generator to point at this branch
  2. Trigger the generator
  3. Change the sandbox generator back again
  4. Merge this before the daily generator kicks in

@ndelangen
Copy link
Member Author

I see, I'll see if I can perform that dance today @JReinhold

Base automatically changed from norbert/not-add-react-init to next December 18, 2023 12:16
@yannbf yannbf added ci:daily Run the CI jobs that normally run in the daily job. and removed ci:daily Run the CI jobs that normally run in the daily job. labels Dec 18, 2023
@yannbf yannbf merged commit 405dfee into next Dec 18, 2023
98 of 100 checks passed
@yannbf yannbf deleted the norbert/add-internalreact16-sandbox branch December 18, 2023 17:37
@ndelangen
Copy link
Member Author

Thank you @yannbf

@github-actions github-actions bot mentioned this pull request Dec 19, 2023
22 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Internal-facing build tooling & test updates ci:daily Run the CI jobs that normally run in the daily job.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants