Skip to content

Fix for storybook fixtures not found error

Kos Palchyk requested to merge kpalchyk/fix-for-storybook-fixtures-not-found into master

What does this MR do and why?

Currently running npm run storybook:start fails if required fixtures are absent.

This MR shifts failure from build-time to run-time. So that absence of fixtures doesn't block from interacting with stories that don't need particular fixture.

This MR also fixes some rendering warnings that polluted browser console.

Screenshots or screen recordings

Before After
image image
image

How to set up and validate locally

Delete or rename your local fixtures folder (path.resolve(ROOT, 'tmp/tests/frontend', IS_EE ? 'fixtures-ee' : 'fixtures')).

Start storybook npm run storybook:start — you should see errors above, but stories should still be accessible.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports