Closed moeriki closed 5 years ago
Found the issue. If Gatsby warns us about "conflicting field types" we should pay attention. This is data that's not being loaded correctly.
warn There are conflicting field types in your data.
If you have explicitly defined a type for those fields, you can safely ignore this warning message.
Otherwise, Gatsby will omit those fields from the GraphQL schema.
If you know all field types in advance, the best strategy is to explicitly define them with the `createTypes` action, and skip inference with the `@dontInfer` directive.
See https://www.gatsbyjs.org/docs/actions/#createTypes
wordpress__POST.taxonomies.rest_base:
- type: boolean
value: false
- type: string
value: 'categories'
wordpress__POST.taxonomies.rest_controller_class:
- type: boolean
value: false
- type: string
value: 'WP_REST_Terms_Controller'
I ignored this for too long apparently. If you need any of the above data adapt ./wp-normalize.js
to your needs.
https://foursevens.be/wp-json/wp/v2/posts?status=publish&per_page=100