This change broke our app yesterday when Slash upgraded because getInterface() suddenly disappeared, which we’re relying on in several places. It’s not that big of an inconvenience to switch to queryInterface(), but there’s a bigger problem. We have a handful of situations where we want to enforce …

Uniqueness for @id fields on interface

JatinDevDG (Jatin Dev ) Split this topic April 7, 2021, 9:17am 6

A post was merged into an existing topic: Multiple ID issue

Topic		Replies	Views
@id directive and interfaces GraphQL kind:question , status:accepted , ticket:created , area:interface	4	1030	November 30, 2020
20.11.1 breaks our project with custom ID types GraphQL	3	950	April 20, 2021
[Bug] Allow type to implement interfaces with same fields GraphQL kind:bug	7	611	October 11, 2021
Was there a change to generated queries with @id directives in v20.11.1? GraphQL	8	1309	April 20, 2021
RFC: Allow multiple unique fields in graphql schema GraphQL	11	2728	March 22, 2021