Wp-graphql-woocommerce: Documentation of breaking change: "typeId" fields replaced by "databaseId"

Created on 20 Oct 2020  路  2Comments  路  Source: wp-graphql/wp-graphql-woocommerce

Describe the bug

Hey @kidunot89, just upgraded from 0.5.1 to 0.6.1 and during testing found this breaking change (for me at least) that wasn't highlighted in the CHANGELOG.md:

https://github.com/wp-graphql/wp-graphql-woocommerce/commit/449d3b16743aaa65de3eeb5cbfe7cc5fa589da99

I did a quick pass on the documentation too, and there doesn't seem to be any significant mention of using things like productId, variationId, etc. so that's good.

One instance here, but its interpretation is ambiguous since productId is a valid input parameter for mutations:
https://woographql.com/guides/create-react-app/1-creating-the-product-list

Not sure if this is easier for you to fix, or if you'd like a PR for your documentation. Happy to help. Thanks!

docs help wanted

Most helpful comment

postTypeId fields have been replaced with databaseId for consistency with the WPGraphQL core post type design and so support could be add for some of core Interfaces on the Product, ProductVariation, and Order types.

All 2 comments

:man_facepalming: My bad, I made those changes early on and forgot to document them in the release summary.

@ardiewen Any and all help on documentation are welcome :100:

postTypeId fields have been replaced with databaseId for consistency with the WPGraphQL core post type design and so support could be add for some of core Interfaces on the Product, ProductVariation, and Order types.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

dpacmittal picture dpacmittal  路  5Comments

mohaimenmahi picture mohaimenmahi  路  5Comments

jacobarriola picture jacobarriola  路  5Comments

pmventura picture pmventura  路  3Comments

IRediTOTO picture IRediTOTO  路  4Comments