feat(gatsby-source-wordpress): auto-alias any field named fields to prevent conflicts with Gatsby core
#31526
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
gatsbot
bot
added
the
status: triage needed
…-wordpress-ninja-forms-field
TylerBarnes
approved these changes
May 21, 2021
TylerBarnes
changed the title
fields to prevent conflicts with Gatsby core
|
All the failing tests are unrelated and the WP tests pass so I'm gonna merge. A canary is published in |
LekoArts
removed
the
status: triage needed
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
@TylerBarnes PR to add an alias for the field 'fields' when sourcing form from Wordpress using wp-graphql-ninja-forms as discussed in the slack channel.
Documentation
Related Issues