Querying same field w/ and w/o attributes for different union types results in error

Query:

{
  curatedList {
     ...on Program {
        title(lang: "fi")
     }

     ...on Article {
        title
     }
  }
}

Error:

Fields title conflict because they have differing arguments.

Should it really work like that, or is this a bug?

Article and Program are both members of union type Content

[jbmikk]

This is so bad, I have several TS interfaces and I expect my results to match those interfaces, if I start aliasing the unions then they won’t match and I’m going to have to convert the results to match the TS interfaces.

I’m going to use just a plain JSONResolver for the conflicting fields. Graphql should support unions for scalars, and if that goes against the spec, then the spec is probably wrong and should be fixed. There should be at least a way to relax this or provide a solution that does not imply aliasing or having to interpret the results after in any way.

Union types are ambiguous by definition, you either support them or you don’t.

[leebyron]

I think we could probably improve this if two fields are known to never “merge”. In this case, the two types are Object types and in no condition would both “title” fields be queried for the same object.

We should be a bit smarter about this (likely common) case