Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Removing named connections graphql API

See original GitHub issue

Describe the bug

Removing named connections of models throws Cannot perform more than one GSI creation or deletion in a single update. Someone who hasn’t experienced this would think that he/she needs to remove those one by one, but doing so will throw Found one half of connection "<ModelName>" at <ModelName>.<field> but no related field on type <ModelName>.

To Reproduce Steps to reproduce the behavior:

Create a two models, that look like so:

type ModelOne
  @model
  @searchable
  @auth(rules: [{ allow: public, provider: apiKey }, { allow: private }]) { {
  id: ID!
  testField: String
  modelTwo: ModelTwo @connection(name: "ModelOneTwoConnection", keyField: "modelOneId")
  createdAt: AWSDateTime
  updatedAt: AWSDateTime
}

type ModelTwo
  @model
  @searchable
  @auth(rules: [{ allow: public, provider: apiKey }, { allow: private }]) { {
  id: ID!
  modelOneId: String
  testFieldAgain: String
  modelOne: ModelOne @connection(name: "ModelOneTwoConnection", keyField: "modelOneId")
  createdAt: AWSDateTime
  updatedAt: AWSDateTime
}

I tried to push this and the connection didn’t work, modelTwo field will always be null when I query ModelOne, I suppose this could only be done in a “belongsTo” fashion where I have to do this instead:

type ModelOne
  @model
  @searchable
  @auth(rules: [{ allow: public, provider: apiKey }, { allow: private }]) { {
  id: ID!
  testField: String
  modelTwo: [ModelTwo] @connection(name: "ModelOneTwoConnection", keyField: "modelOneId")
  createdAt: AWSDateTime
  updatedAt: AWSDateTime
}

type ModelTwo
  @model
  @searchable
  @auth(rules: [{ allow: public, provider: apiKey }, { allow: private }]) { {
  id: ID!
  modelOneId: String
  testFieldAgain: String
  modelOne: ModelOne @connection(name: "ModelOneTwoConnection", keyField: "modelOneId")
  createdAt: AWSDateTime
  updatedAt: AWSDateTime
}

But I decided to remove the connection all together to try a different approach.