-
Notifications
You must be signed in to change notification settings - Fork 77
Release/v0.4.0 #81
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
Merged
Merged
Release/v0.4.0 #81
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… serviced - This validates the Auth Token when the GraphQL Request is being initiated, and if it's invalid the request does not execute and a 403 status is returned.
- This updates the mutations to expect a User model to be passed through instead of a WP_User object - This also updates some of the errors to be more clear, passing through WP_Error messages - This also returns null when the user cannot access the JWT Secret instead of throwing an error.
…ed-after-user-registered #69 - JWT Tokens could not be returned after regiserUser mutation
…iblity for passing WP_User or User (model) through to some resolvers
…ed-after-user-registered Bug/#69 jwt could not be returned after user registered
…ed-after-user-registered #69 - Backward Compatibility fixes for playing nice with WPGraphQL for WooCommerce
# Conflicts: # src/Auth.php
Docs/add all mutations
…69-jwt-could-not-be-returned-after-user-registered # Conflicts: # wp-graphql-jwt-authentication.php
kidunot89
approved these changes
Feb 18, 2020
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.
This resolves the last issue related to WPGraphQL-JWT-Authentication in the WooGraphQL.
Working 100% with WooGraphQL
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Release Notes
Breaking Changes
From a GraphQL Consumer perspective there shouldn't be any breaking changes. The shape of queries and mutations remain the same in this release.
Some internal functions were modified, so for plugins that extend this (i.e. WPGraphQL for WooCommerce) it's best to check your use of internal functions for how changes may affect your code.
If anything, this should fix things that previously broke when updating to WPGraphQL v0.5.0/v0.6.0 support.
New Features
Bugfixes