Multiple types for fields. Conflict when querying.

rene.k3

3 months ago

10

• 

  dribbens

  Payload Team

  3 months ago

  What is the error specifically? I can understand how this would be a problem, but I'm not sure the solution and seeing the error would help.

• 

  rene.k3

  3 months ago

  {"message": "Fields \"link\" conflict because subfields \"type\" conflict because they return conflicting types \"Hero1_Link_type\" and \"Hero2_Link_type\" and subfields \"subtype\" conflict because they return conflicting types \"Hero1_Link_subtype\" and \"Hero2_Link_subtype\" and subfields \"coll\" conflict because they return conflicting types \"Hero1_Link_coll\" and \"Hero2_Link_coll\" and subfields \"rel\" conflict because they return conflicting types \"Hero1_Link_rel\" and \"Hero2_Link_rel\" and subfields \"target\" conflict because they return conflicting types \"Hero1_Link_target\" and \"Hero2_Link_target\" and subfields \"referrerpolicy\" conflict because they return conflicting types \"Hero1_Link_referrerpolicy\" and \"Hero2_Link_referrerpolicy\". Use different aliases on the fields to fetch both if this was intentional."}

• 

  jmikrut

  Payload Team

  3 months ago

  yes, we are releasing a new way to "flatten" the GraphQL types into a single reusable interface

  
  

  
  

  @dribbens we should release that feature ASAP and then comment here

• 

  dribbens

  Payload Team

  3 months ago

  Aye, good call!

• 

  rene.k3

  3 months ago

  Nice. Thanks for help guys.

• 

  dribbens

  Payload Team

  3 months ago

  OK 1.9.0 has it.

  
  

  
  

  Thanks for being patient.

  
  

  
  

  @rene.k3 Give it a shot and let us know

• 

  rene.k3

  3 months ago

  @dribbens It's awesome. It works great. I like the solution. Thanks for the quick turnaround.