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
web: require enabling Chromatic snapshot for every story manually #30331
Conversation
4d0f8e1
to
a7d7185
Compare
a7d7185
to
3a08e9d
Compare
3a08e9d
to
8772e2e
Compare
Codenotify: Notifying subscribers in OWNERS files for diff 9b27c2e...8772e2e.
|
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.
Great to see this! Could it be helpful to also add a note to our docs about testing to mention that Chromatic snapshots are configured to be off by default and share a snippet for how to re-enable it on a specific story?
* list pending invites * added pending invitations for org grapql method * pending invitations page update * added revoke link and copy link * fixed avatar url and gap in pending invites * added resend invite * try/catch on resend invite * Update cmd/frontend/graphqlbackend/org_invitations.go Co-authored-by: Milan Freml <kopancek@users.noreply.github.com> * Update go.sum Co-authored-by: Milan Freml <kopancek@users.noreply.github.com> * Update internal/database/org_invitations.go Co-authored-by: Milan Freml <kopancek@users.noreply.github.com> * `Card`: Use raw values rather than CSS vars (#31233) * web: require enabling Chromatic snapshot for every story manually (#30331) * Update invite null text and differentiate between two cases (#31168) * doc: update Chromatic docs (#31239) * Experimental ref panel: allow users to collapse top-level lists (#31241) This fixes #30974 by allowing users to collapse the "Definitions", "References" and "Implementations" lists. * search contexts: fix query editing and move error alert inside the form (#31232) * fixing review comments it1 * prettify files Co-authored-by: Milan Freml <kopancek@users.noreply.github.com> Co-authored-by: Tom Ross <tom@umpox.com> Co-authored-by: Valery Bugakov <skymk1@gmail.com> Co-authored-by: Philipp Spiess <hello@philippspiess.com> Co-authored-by: Thorsten Ball <mrnugget@gmail.com> Co-authored-by: Rok Novosel <rok@sourcegraph.com>
* list pending invites * added pending invitations for org grapql method * pending invitations page update * added revoke link and copy link * fixed avatar url and gap in pending invites * added resend invite * try/catch on resend invite * Update cmd/frontend/graphqlbackend/org_invitations.go Co-authored-by: Milan Freml <kopancek@users.noreply.github.com> * Update go.sum Co-authored-by: Milan Freml <kopancek@users.noreply.github.com> * Update internal/database/org_invitations.go Co-authored-by: Milan Freml <kopancek@users.noreply.github.com> * `Card`: Use raw values rather than CSS vars (#31233) * web: require enabling Chromatic snapshot for every story manually (#30331) * Update invite null text and differentiate between two cases (#31168) * doc: update Chromatic docs (#31239) * Experimental ref panel: allow users to collapse top-level lists (#31241) This fixes #30974 by allowing users to collapse the "Definitions", "References" and "Implementations" lists. * search contexts: fix query editing and move error alert inside the form (#31232) * fixing review comments it1 * prettify files Co-authored-by: Milan Freml <kopancek@users.noreply.github.com> Co-authored-by: Tom Ross <tom@umpox.com> Co-authored-by: Valery Bugakov <skymk1@gmail.com> Co-authored-by: Philipp Spiess <hello@philippspiess.com> Co-authored-by: Thorsten Ball <mrnugget@gmail.com> Co-authored-by: Rok Novosel <rok@sourcegraph.com>
Context
The Frontend Platform team started looking into ways to limit our Chromatic spending that went out of hand. And as a first remediation measure, we proposed 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.Here's the list of issues to track the progress per team.
Changes
wildcard
andshared
stories.Results
We have 321 snapshots in the Chromatic diff. There's still room for improvement as @eseliger mentioned in batchers PR — we can still merge some stories or disable specific viewports for some of them.