batchers: enable snapshotting for individual stories

[valerybugakov]

Context

Hey team! The frontend platform team started looking into ways to limit our Chromatic spending that went out of hand.

It's a high-priority task. And as a first remediation measure, we propose disabling snapshotting all stories by default. Snapshotting can be enabled for an individual story by adding disableSnapshot: false to story parameters. That way, it becomes a more conscious decision, and engineers can decide what's important to snapshot.

Action required

We ask you to allocate time to go through stories that your team owns and explicitly enable snapshotting for important stories.

Bonus points for stories optimization: instead of having a separate story of each variant of a small component — merge them into one story that shows all component permutations and enable snapshotting only for this story. It decreases the number of snapshots and makes the Chromatic diff easier to review.

[valerybugakov]

@adeola-ak, could you share an estimate of when you might be able to look into this issue?

[adeola-ak]

hi @valerybugakov! I'll look into this today