-
Notifications
You must be signed in to change notification settings - Fork 735
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
History and Headers aren't persisted #317
Comments
I think this is a bit of a deal breaker for people especially if they need to re-enter a I haven't taken a look, but we should be able to figure out what broke this feature using a |
I believe this is the same as mine #312 -- If so, I can the "headers" bit there and we can close this one? |
Thanks for reporting @danwkennedy ! |
Hey, I had reported this days before :D |
Can't wait for this to be fixed, to be honest. |
This should be fixed in |
Nice! I’ll bump the version in |
This issue pertains to:
What OS and OS version are you experiencing the issue(s) on?
MacOS High Sierra
What version of graphql-playground(-electron/-middleware) are you experience the issue(s) on?
graphql-playground-middleware-koa: 1.3.6
What is the expected behavior?
The previous version we were on persisted the query history and headers when the page was refreshed.
What is the actual behavior?
The headers and history are cleared when the page refreshes. This causes some churn with Authorize headers needing to be set again in the case of the headers clearing. The history also becomes unusable since you can't see your history from previous development sessions.
What steps may we take to reproduce the behavior?
The text was updated successfully, but these errors were encountered: