-
Notifications
You must be signed in to change notification settings - Fork 974
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
Add support for Storybook #742
Conversation
@RobertBroersma I'm going to be using your GraphQL msw mocking abilities over here :) |
Hi @peterp, let us know if need any help or advice! PS I recently created this document with some thoughts about how we are thinking about data mocking in Storybook (we want to add a docs page on it soon), and would be interested you are thinking about it at your end. |
Ooooh @tmeasday Thanks for this! We started using Mock Service Worker for our tests, and it's pretty amazing for mocking GraphQL, rest and HTTP requests. It's great because it's client agnostic and has a very minimal API design! I should be done with this PR soon and I would love to show you the approach, maybe we can jump on a call early next week? |
@peterp I'll take a look at this this weekend and start writing some docs! |
@jtoar Awesome! Hit me up if you have any questions! |
Let's do it @peterp -- I'll send you an email |
Hey Guys, are there any tracking issues for "How would a user overwrite the Providers?" or "How would the user add addons" ? |
Storybook allows you to develop your components in isolation, away from all the conflated cruft of your real app.
"Props in, views out! Make it simple to reason about."
yarn storybook
command*.stories.js
,*.stories.tsx
, and*.stories.jsx
Generators
Configuration options for users
Debug