In the first pass, we see all of the screens, but always show the initial build screen, then have the user create a second build. This updates logic to show the catchAChange screen if the selectedBuild exists.
There are some rough edges where it doesn't work as intended. It doesn't include the Nice. You saved your stories as a test baseline. step where it prompts the user to go onto catch a change because it no longer uses state variables.
Cannot test the flow locally because it encounters the following error:
Publish your built Storybook
→ Validating Storybook files
Publishing your built Storybook
→ Retrieving target location
→ Starting publish
→ [ ] 0%
→ [============= ] 65%
Publish complete in 17 seconds
→ View your Storybook at https://652865507e138292e0cf0821-xxljdazcbj.chromatic.com
Verifying your Storybook
→ This may take a few minutes
→ [* ]
✖ Failed to extract stories from your Storybook
This is usually a problem with your published Storybook, not with Chromatic.
Build and open your Storybook locally and check the browser console for errors.
Visit your published Storybook at https://652865507e138292e0cf0821-xxljdazcbj.chromatic.com
The following error was encountered while running your Storybook:
Cannot destructure property 'provider' of 'undefined' as it is undefined.
→ Failed to publish build
In the first pass, we see all of the screens, but always show the initial build screen, then have the user create a second build. This updates logic to show the catchAChange screen if the selectedBuild exists.
There are some rough edges where it doesn't work as intended. It doesn't include the
Nice. You saved your stories as a test baseline.step where it prompts the user to go onto catch a change because it no longer uses state variables.Cannot test the flow locally because it encounters the following error: