-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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(gatsby-source-wordpress): Ability to set a custom rest api route prefix #20998
feat(gatsby-source-wordpress): Ability to set a custom rest api route prefix #20998
Conversation
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.
Hey @crock! This is great, thank you for your contribution!!
Just one comment above. Once I fixed that locally it worked perfectly.
Can you also add a note to the README about the new plugin option?
…urce-wordpress/20995/custom-rest-api-route-prefix
…oute-prefix' of https://github.com/gatsbyjs/gatsby into feature/gatsby-source-wordpress/20995/custom-rest-api-route-prefix
Ahh, couldn't figure out why I couldn't merge this. @gatsbyjs/learning needs to review since the README was updated, then we should be good. Thanks again @crock 👍 |
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.
Looks good to me! Thanks for updating the README.
Description
Adds a configuration option called
restApiRoutePrefix
that allows you to set a custom route prefix if one of your WordPress plugins changed it fromwp-json
.wp-json
is left as the default value.Related Issues
#20995