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
As an admin user logged into the WordPress dashboard using the GraphiQL IDE, I would like to be able to execute queries as a public (non-authenticated) user or as the user I'm logged into WordPress as.
Acceptance Criteria
Match existing functionality
Button should exist near the other buttons (play, prettify, etc) that allows the user to click to toggle authentication state
User should be able to identify what state the execution is currently in (authenticated vs non-authenticated)
User's gravatar (if available) should show in the button, or a fallback generic user icon if no gravatar is available.
Button should be filterable (users could remove it or override it if they wanted to via a filter) This will be added as we work towards making things pluggable
NOTES:
Current version of the auth switch is written as an extension. While it could be "built-in" to the greater codebase, it was a good way to "prove" the hook/filter system and I think we should follow that pattern when we re-build it. We may refactor in the next phase of this project
The text was updated successfully, but these errors were encountered:
User Story
As an admin user logged into the WordPress dashboard using the GraphiQL IDE, I would like to be able to execute queries as a public (non-authenticated) user or as the user I'm logged into WordPress as.
Acceptance Criteria
Button should be filterable (users could remove it or override it if they wanted to via a filter)This will be added as we work towards making things pluggableNOTES:
Current version of the auth switch is written as an extension. While it could be "built-in" to the greater codebase, it was a good way to "prove" the hook/filter system and I think we should follow that pattern when we re-build it.We may refactor in the next phase of this projectThe text was updated successfully, but these errors were encountered: