You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The state in the graphiql playground for Variables and Headers tab no longer persists thru browser sessions. This is a slight annoyance as I like to store csrf tokens, etc there while developing & debugging
Your Example Website or App
n/a
Steps to Reproduce the Bug or Issue
To repro:
Open graphiql that ships with latest version of yoga
Put something in headers sub-tab
Close browser tab/window for this session
Go back to api playground and see that Headers tab is now blank
Expected behavior
I expected the headers info to persist across sessions, as it used to with old versions of yoga
Screenshots or Videos
No response
Platform
OS: macOS
Browser: Chrome 111.0.5563.146
Yoga: latest
Additional context
No response
The text was updated successfully, but these errors were encountered:
Sorry but I'm not adding a lot here but just labeling it according to our new Contribution Guide and issue flow.
It seems already got into stage 3 thanks to @Akryum who found a working solution, that is a huge push for us!
The next stage 4 phase is about actually implement this solution in a PR.
If anyone wants to help, check out the instructions here on how to clone the repo and gradually become aware of the internal codebase.
We would love to help with any questions you might have!
Thank you and sorry that this comment is not a complete solution (yet).
Describe the bug
The state in the graphiql playground for Variables and Headers tab no longer persists thru browser sessions. This is a slight annoyance as I like to store csrf tokens, etc there while developing & debugging
Your Example Website or App
n/a
Steps to Reproduce the Bug or Issue
To repro:
Expected behavior
I expected the headers info to persist across sessions, as it used to with old versions of yoga
Screenshots or Videos
No response
Platform
Additional context
No response
The text was updated successfully, but these errors were encountered: