In the graphql_map_input_fields_to_wp_query filter, the $post_type is the last parameter. This is inconsistent with the other graphql_map_input_fields_* filters. For example in graphql_map_input_fields_to_get_terms the $taxonomy parameter is the third parameter (while the $context & $info parameters are the last two in all of the graphql_map_input_fields_* filters). For consistency sake, i

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

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/

Replace deprecated methods DataSource::resolve_post_object with $context->get_loader('post')->load($id)