Better Fragment Handling

[brettjurgens]

from this comment by @BinaryMuse #76 (comment):

export interface MyTestQuery {
  resource:
    | SelectionOnResource &
        Partial<IFragmentIssue> &
        Partial<IFragmentOrganization>
    | null;
}

export interface IFragmentIssue {
  __typename: string;
  id: string;
  title: string;
  author: SelectionOnAuthor | null;
}

export interface IFragmentOrganization {
  __typename: string;
  orgName: string | null;
}

but since we know statically what all the typenames are, it could be something like

export interface MyTestQuery {
  resource:
    | IFragmentIssue
    | IFragmentOrganization
    | DefaultSelectionOnResource
}

export interface IFragmentIssue {
  __typename: "Issue";
  id: string;
  title: string;
  author: SelectionOnAuthor | null;
}

export interface IFragmentOrganization {
  __typename: "Organization";
  orgName: string | null;
}

export interface DefaultSelectionOnResource {
  __typename: string;
}

[brettjurgens]

Completely off the top of my head and this might be inaccurate, but my thoughts are:

• need to get specific __typename (already going to do)
• in order to do an OR, we probably need to:
  • flatten fragments without a ... on Type
  • ensure that all cases are covered (might not be necessary if OR'd with non-fragment selection)
  • either:
    • extend fragments with the default selection, without the __typename
    • OR the fragments and AND with the selection on root type (minus __typename)