@dgraph directive does not work as expected with union types

[abhimanyusinghgaur]

@christian-roggia

I also rechecked the documentation, and it seems like it is not possible to set the @reverse predicate in the schema through GraphQL but only through DQL. I read through some tickets related to this particular corner case and wonder whether you are still considering adding the “@dgraph” directive in the format of “@dgraph(pred: “Item.owner”, reverse: true)”.

I think the best expectation is that the original schema should work as it is. That should add the @reverse directive, but it seems like a bug. So, we will fix the original issue itself.

@christian-roggia

I also wonder whether there is any plan to allow @hasInverse on union types at all or whether the @id directive will be allowed to be declared in two interfaces if implemented with exactly the same fingerprint (like it works for the ID type).

We don’t have any plans for allowing either of these behaviors because of the associated issues with them as mentioned in the posts you have linked.

@christian-roggia Thanks for finding this corner-case.
Cheers!