Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v1.4.0 #141

Merged
merged 12 commits into from
Jul 2, 2024
Merged

v1.4.0 #141

merged 12 commits into from
Jul 2, 2024

Conversation

gmac
Copy link
Owner

@gmac gmac commented Jun 9, 2024

What

Introduces composite keys and composite arguments, making this type of stitching possible:

interface FieldOwner {
  id: ID!
  type: String!
}
type CustomField {
  owner: FieldOwner!
  key: String!
  value: String
}
input CustomFieldLookup {
  ownerId: ID!
  ownerType: String!
  key: String!
}
type Query {
  customFields(lookups: [CustomFieldLookup!]!): [CustomField]! @stitch(
    key: "owner { id type } key",
    arguments: "lookups: { ownerId: $.owner.id, ownerType: $.owner.type, key: $.key }"
  )
}

Includes

Resolves #139.

Minor breaking changes

  • Resolver key argument aliases are no longer supported. What was @stitch(key: "myArg:myKey") becomes @stitch(key: "myKey", arguments: "myArg: $.myKey").
  • Regenerate all supergraph exports for latest schema formats.
  • Bust all query plan caches for latest plan format.

@gmac gmac changed the title v1.14.0 v1.4.0 Jun 12, 2024
@gmac gmac merged commit 2d785ec into main Jul 2, 2024
7 checks passed
@gmac gmac deleted the v1_14_0 branch July 2, 2024 02:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support composite keys/inputs
1 participant