-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
Server: Initial support for @storybook/server #9722
Conversation
Template based server side rendering Added a bunch of stories to the example app
* More snapshot tests * Fixed some bugs * Added kitchen sink example to demo app
…ybook into jonspalmer-storybook_server
Oop, actually I can push to your branch, closing this. |
the mdx.tsx stuff really has nothing to do with this PR. That was @shilman piggy backing on the PR. I'd leave it to him to comment. |
The |
I guess the comment implies as "neither did the story" (which is true, the story didn't change if force render is true) that the behaviour is intended. Let's leave it for now. |
Going to merge from this branch |
I can't commit to #9250 so this is a follow up PR to try and get it over the line
@jonspalmer there are still two unresolved comments on that PR that we need to sort out:
Is this a mistake or did I misunderstand: Initial support for @storybook/server #9250 (comment)
Do we need to deal with this TODO: https://github.com/storybookjs/storybook/pull/9250/files/be4d06c0cd69b2ed4a79ad390852770bfd6ccfeb#diff-83aae226cfb73b52d12dfd37ae15a411?
Also a change to
mdx.tsx
got dropped becausegenerateHrefWithHash
doesn't exist any more. I'm not sure if that's going to be a problem but I'll have a proper play with this once the above two questions are resolved.