-
Notifications
You must be signed in to change notification settings - Fork 2
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
Send a sessionId on graphql requests #22
Conversation
Oh, hey I noticed something odd here... I accepted my own local build on another branch for the no build story, and it seems like it's now being applied as the baseline for merging to main... Is that expected? |
@weeksling it looks like you accepted it on this branch: https://www.chromatic.com/test?appId=6480e1b0042842f149cfd74c&id=64d6994da701c906f8bc611b -- I reached out on slack to try and nail down what happened exactly. I won't merge this until we figure it out just for record keeping (I think this PR is good to merge though, apart from possible messed up baselines) |
So we can track sessions in the index (PR to follow). The CLI already sends a
sessionId
in a very similar way: https://github.com/chromaui/chromatic-cli/blob/cfb2f280a92b5a01532ca625b0b55b180d8de37b/node-src/index.ts#L48📦 Published PR as canary version:
0.0.24--canary.22.6913426.0
✨ Test out this PR locally via:
npm install @chromaui/addon-visual-tests@0.0.24--canary.22.6913426.0 # or yarn add @chromaui/addon-visual-tests@0.0.24--canary.22.6913426.0