feat(gatsby-source-wordpress): add jwt_base_path option #11425
Merged
Conversation
This file contains 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
…t in auth options, to support other wordpress jwt plugins
wardpeet
changed the title
|
@rotexhawk Thanks for this PR. Could you perhaps create an issue too with some more information about which plugins and why this is necessary. Code looks great! |
wardpeet
added
type: feature or enhancement
status: awaiting author response
|
Thanks. I added this issue: #11488 |
wardpeet
approved these changes
Feb 1, 2019
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.
Description
Removes hardcoded JWT token path in gatsby-source-wordpress and passes it in auth options, to support other Wordpress JWT plugins.
Test Passed and the functionality works locally.