Replies: 4 comments
|
This is a known issue with the new In the interim, you apply the following PRs to your local copy of |
0 replies
|
Thanks Dovid, got it working 👍
…On Mon, 15 Mar 2021 at 12:10, Dovid Levine ***@***.***> wrote:
This is a known issue with the new gatsby-source-wordpress, and sadly
it's not as simple as simply renaming the property to something other than
field, since Union types in general are broken.
In the interim, you apply the following PRs to your local copy of
gatsby-source-wordpress:
gatsbyjs/gatsby#29717 <gatsbyjs/gatsby#29717>
gatsbyjs/gatsby#29751 <gatsbyjs/gatsby#29751>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#77 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARTG6ZIE36V2U27XO5JUSVLTDX2LFANCNFSM4ZGMX22Q>
.
|
0 replies
|
v0.5.0 is |
0 replies
|
Awesome, thanks for the update 😀
…On Sat, 24 Apr 2021 at 15:32, Dovid Levine ***@***.***> wrote:
v0.5.0 is gatsby-source-wordpress compatible.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#77 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARTG6ZKE7IPSG2KVV73L6LDTKLI7BANCNFSM4ZGMX22Q>
.
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi,
Gatsby reserves the field "fields". Is it easy enough to rename this (e.g. formFields) when registering the form to GraphQL? If so, if anyone can point me in the right direction that would be much appreciated 🙂
Thanks
All reactions