egghead.io
  1. 1
    Course Intro for Designing GraphQL Schemas
    44s
  2. 2
    Setup an Apollo GraphQL Server with automatic Mocking
    2m 22s
  3. 3
    Kicking off a GraphQL Schema Design Process
    2m 15s
  4. 4
    Naming Conventions for Query Fields in GraphQL
    4m 40s
  5. 5
    When and Why to use Nullable vs Non-nullable Fields in GraphQL
    3m 26s
  6. 6
    Evolving a GraphQL Schema incl. Breaking Changes without affecting a Single User
    2m 12s
  7. 7
    Naming Conventions for Fields with GraphQL Aliases in Mind
    3m 7s
  8. 8
    Paginate Entries using the Connection Specification
    11m 6s
  9. 9
    Extending GraphQL Connections with additional Fields and Arguments
    4m 8s
  10. 10
    Naming top-level Query Fields in GraphQL
    2m 39s
  11. 11
    Mutation Input and Payload Structure in GraphQL
    4m 50s
  12. 12
    Design GraphQL Mutations by focusing on the Domain rather than the Data Model
    5m 10s
  13. 13
    Optimising GraphQL Mutations for Static Usage
    1m 56s
  14. 14
    GraphQL Mutations to update Connections
    2m 3s
  15. 15
    Tradeoffs when designing GraphQL Mutations to update multiple Properties on one Entity
    5m 37s
  16. 16
    Course Outro for Designing GraphQL Schemas
    36s

GraphQL Mutations to update Connections

Nik Graf
InstructorNik Graf
  • graphql
    GraphQL

Share this video with your friends

Send Tweet

A common requirement for connections is to add and remove items. We could go with two separate mutations: add & remove versus a single update mutation. In almost all situations it's better to have two separate mutations and in this lesson we explore why.

illustration for Designing GraphQL Schemas

Course

Designing GraphQL Schemas

Build your Developer Portfolio and climb the engineering career ladder.
  • Search
  • Talks
  • Podcasts
  • Machine
  • Pricing
  • Store
©egghead.io
Terms & Conditions