Plugin: restore documentation path on page/schema reload
See original GitHub issueAt the moment, reloading the page is the only way to reload changes to the schema/documentation of said schema. It is fine in production, since schema will not change every second, and mostly fine in development (of a GraphQL endpoint) because the state is mostly kept.
However, the documentation resets, which means I either have to click the correct sequence of types, or use the search field, every time I refresh the page.
I think it would be very intuitive to reload the documentation as it was before refreshing the page. This could be done via a ?documentation=...
query string (in addition of ?query=...
). Any thoughts? 😃
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:8 (6 by maintainers)
Top Results From Across the Web
git-restore Documentation - Git
DESCRIPTION. Restore specified paths in the working tree with some contents from a restore source. If a path is tracked but does not...
Read more >Plugins mysteriously disappear after restart or plugins are ...
1) Restore the plugins manually (from the plugin repository), or use the standard upgrade procedure. If restoring to an already functioning ...
Read more >Create 2022.3.1 - NVIDIA Omniverse Documentation
Convert 102 asset not reset on Stop animating. Rename the timesample to animation curve key window. Add stage load activity.
Read more >Restore - IBM
The restore command obtains copies of backup versions of your files from the IBM Spectrum Protect server, or inside a backup set.
Read more >Backing up and Restoring Files | iFIX 6.1 Documentation
To help you manage your iFIX files, use the iFIX Backup and Restore feature. ... you will need to make sure you update...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
We’ve just formed the GraphiQL Working Group, and this is one of the things that came up in the first meeting (I’m particularly interested in it as we already have a hack we’ve been using for a couple years in PostGraphile, though that only applies to hot-reload, not full page reload). This is definitely on the radar, but we cannot commit to a time-frame.
I think a good litmus test for whether something belongs in the URL is the answer to the question:
If the answer is “yes”, then it makes sense for it to live in the URL. The
query
param evidently satisfies that criterion, and the ability to deep-link to documentation as well seems pretty interesting too. Having said that, the URLs can already be pretty monstrous, so we may also want to consider other solutions to that particular deep-linking use case (for example, a link icon you can click to get the link as opposed to automatically updating the location bar like we do with queries).Either way, storing it in local storage sounds fine too, I would think.