this post was submitted on 10 Sep 2023
15 points (100.0% liked)

Programming

17450 readers
161 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
MaungaHikoi@lemmy.nz
15
Anyone using Storybook + React? How do you like it? Is it as bad as it seems at first? (sh.itjust.works)
submitted 1 year ago by WheeGeetheCat@sh.itjust.works to c/programming@programming.dev
10 comments fedilink hide all child comments
 

I was pretty excited to add storybook to my project, but after setting up my basic components like buttons and moving on to higher level components that render slices of state using selectors .... I have regrets.

Is it me or is it really hard to 'storybook-i-fy' react components using selectors? I found this tutorial on the Storybook site and it looks like the preferred pattern is to duplicate your store in your storybook file? That can't be right, can it?

Someone talk me out of taking Storybook out back and uninstalling it from my repo.

you are viewing a single comment's thread
view the rest of the comments
[–] pastelmind@programming.dev 2 points 1 year ago

Stories are like tests. You need to mock your stores if you want to isolate your stories. Just like how you mock HTTP APIs or database connections when writing tests. This is the cost of writing testable code.