Multiple inline fragments - & vs |

On a query like this

      dishes {

        ... on RecipeDish {
          id
          recipeId
        }

        ... on IngredientDish {
          id
          ingredient 
        }
      }

The result is

export type Dishes = RecipeDishInlineFragment & IngredientDishInlineFragment

But it should be

export type Dishes = RecipeDishInlineFragment | IngredientDishInlineFragment

Am I not mistaken?

Thanks

[iamdanthedev]

@altschuler I wrote the comment above being sure that union is & instead of I %)

apollo-codegen produces a union for instance, however it doesn’t generate it in a handy form this library does (with subtypes, instead of one long type), which makes it (apollo-codegen) not that useful

export type MenuDishFragmentFragment = {
  dishes:  Array<( {
      __typename: "RecipeDish",
      id: string,
      recipeId: string,
    } | {
      __typename: "IngredientDish",
      id: string,
      ingredient:  {
        productId: string,
      },
    }
  ) >,
};

[dotansimha]

ok, so I did some work on it, and the results will be: FIELDS & FRAGMENT_SPREAD & (INLINE_FRAGMENT | INLINE_FRAGMENT | INLINE_FRAGMENT). Since fragment spread are in use to specify list of fields in a context of a type, and inline fragments are in use to declare different selection set for interface/union.