-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
feat: maintain DocExplorer stack on schema update #3012
Conversation
🦋 Changeset detectedLatest commit: c09abd1 The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
The latest changes of this PR are available as canary in npm (based on the declared |
I assume this is due to the token issues we're facing; hopefully we can get this sorted out soon after tomorrows WG meeting 👍 |
@benjie yep, just need my |
@benjie just tested manually and it works! thanks for this :) |
@@ -87,4 +107,134 @@ describe('DocExplorer', () => { | |||
const errors = container.querySelectorAll('.graphiql-doc-explorer-error'); | |||
expect(errors).toHaveLength(0); | |||
}); | |||
it('maintains nav stack when possible', () => { |
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.
<3
Previously:
I'm not sure what the need for resetting the explorer stack is, so I've raised this PR to begin discussions. I believe that the doc explorer should only be reset when an incompatible schema is loaded, and even then we should aim to keep the compatible parts of the stack where possible. I've attempted to achieve this (and included tests for the same) in this PR.