-
Notifications
You must be signed in to change notification settings - Fork 91
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
FIX/NEW: Stories are now fetched dynamically from related modules #901
FIX/NEW: Stories are now fetched dynamically from related modules #901
Conversation
Fixes #785? |
With one slight caveat - modules still need to opt-in with a file in the root of the module. |
Good enough =) nice one |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool! Haven't tested it. I also don't think this needs to be a patch release, retarget at 1
branch?
70937d7
to
899814a
Compare
I should re-target this at |
Modules that stories need to be gathered from should have a .ss-storybook.js configuration file in their root directory
Co-Authored-By: Robbie Averill <robbie@averill.co.nz>
Caused by trying to realpath a non-existent file. This commit also updates code docs
899814a
to
c11d0f3
Compare
Ok that's retargetted now. I've addressed the feedback too. Hopefully we can get this merged for modules to use |
Modules that stories need to be gathered from should have a .ss-storybook.js configuration file in their root directory
I'll add some documentation in a framework PR, and then I'll add the
.ss-storybook.js
to asset-admin too.I can rebase this against the minor branch if required but as this is dev changes I thought it'd be nice to have this storybook enhancement in place for fixing bugs or developing features in modules based on admin@1.4
Fixes #785
Related PRs: