GraphQL

As a user, I would like to be able to query a comment by database id.

Currently, the comment query doesn't allow for different id types (such as database id), but many other "single node" entry fields in the Graph support an idType field, such as:

{
  post( id: 123, idType: DATABASE_ID ) { __typename, id }
  contentNode( id: 123 idType: DATABASE_ID ) { __typename, id }
}

A while back I introduced #871 which gave the ability to provide a custom edge for the @belongsToMany directive. This, in turn, made it possible include pivot custom data within the edge.

I'm realizing now that the @rename directive wasn't taken into account for handling the custom edge data. This should be a very simple fix which I'm happy to tackle. I just wanted to make an issue so I don

WP-GraphQL-Woocommerce can't detect the product categories with different term_id and term_taxonomy_id IDs in wp_term_taxonomy table.

By default, the term_id and term_taxonomy_id have the same ID value in wp_term_taxonomy table.
For example:

term_taxonomy

Updates the requirements on doctrine/annotations to permit the latest version.

See this ticket as a main reference and for discussions: wp-graphql/wp-graphql#1535

WordPress VIP has pretty high coding standards and everyone who will work with VIP in the future will face the same problems as our team right now. It would be great if we could get coding standards up and running with VIP's standards.

Ideally we could setup PHP_Codesniffer with all

The Settings accepts several options which modify permalinks:

• Single endpoint path
• Persisted query base slug
• Other similar ones

We must validate that the input values are correct. Things to watch out for:

• Unsupported chars: !@#$%*()+='"...
• Too long: thispathistoolongthatthebaseslugcantprocessit
• Many instances of // together: /graphql-query/base//path/

The Settings accepts several options which modify permalinks:

• Single endpoint path
• Persisted query base slug
• Other similar ones

We must validate that the input values are correct. Things to watch out for:

• Unsupported chars: !@#$%*()+='"...
• Too long: thispathistoolongthatthebaseslugcantprocessit
• Many instances of // together: /graphql-query/base//path/