GraphQL 'whereType' is no longer working as expected with content relationships

[services (Built by Field)]

I'm experiencing an issue in one of my repositories where when I query using the where filter on a content relationship within a group. The query worked as of a few days ago, but quietly broke today. It appears to have broken within your API at the point of generating the schema, since I can no longer find the option within the GraphQL explorer either!

Screen Shot 2021-01-19 at 4.45.02 PM|690x89

May be related to this issue: Content relation returns null in document query graphql - #5 by Pau

[Fares]

Hi Brett,

Welcome to the Prismic community,

Can you please tell us where do you get this error shown in the screenshot? is it in the browser console of the GraphQL explorer?

If that is the case then can please share with me (in a private message if necessary the name of your repository) as well as a full query to be able to reproduce the issue on my side?

Looking forward to your reply,
Fares

[Fares]

Got your private message, I will investigate and get back to you.

[Fares]

Hi,

I've checked with my team, and it turns out that it isn't possible to query by Content Relationship field inside a Group field.

And here is where this is explained in our GraphQL documentation.

I know that this is possible in the Rest API so I will create an issue/feature request in our tracker to check if it is possible to implement.

Also, I think even if this is not possible the error you are getting is not self-explanatory and need to be improved because the field levers exist in your schema

so I will add it to the created issue

Best,
Fares

[services (Built by Field)]

Hey Fares,

I think my confusion comes from the fact that this feature was in fact possible as of a few days ago-- since the same code was compiling and the GraphQL API used to create these fields.

I'll change the approach we use on the site, but it's frustrating to have a feature silently deprecated like that.

Cheers,

B

[Fares]

Hi Brett,

I've checked with our dev team, and in fact, this wasn't a feature but a regression, I will create a feature request and send it to our production team and notify @features-team to check if we can have it back.