field tags causes naming conflict and throws an save error

[ykethan]

Before opening, please confirm:

• I have searched for duplicate or closed issues.
• I have read the guide for submitting bug reports.
• I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
• I have removed any sensitive information from my code snippets and submission.

App Id

d27ep6bgfd7ubg

Region

us-east-1

Environment name

dev

Figma File Version (if applicable)

No response

Amplify CLI Version

No response

If applicable, what version of Node.js are you using?

No response

What operating system are you using?

No response

Browser type?

No response

Describe the bug

consider the following model

type Product @model @auth(rules: [{allow: public}]) {
  id: ID!
  name: String
  description: String
  price: String
  category: String
  tags: [String]
  Inventories: [Inventory] @hasMany(indexName: "byProduct", fields: ["id"])
  cartID: ID @index(name: "byCart")
}

this causes the form to render but any changes to the form causes an error

The number of resources passed must be greater than 0 and less than 100.

refreshing the page causes the form to not open at all.

workaround:

renaming the field tags to anything else works as expected.

Expected behavior

provide a better error message and load field that contains tags

Reproduction steps

1. create a data model with a tags field and deploy
2. create a form with the model
3. make a new field on form
4. observe save error

Project Identifier

No response

Additional information

No response

[Eliav2]

have same issue over here, with the model

type Question @model {
  id: ID! @index(name: "questionsByDate",queryField: "questionsByDate",sortKeyFields: ["createdAt"])
  question: String!
  answer: String!
  incorrectAnswers: [String!]!
  tags: [String!]!
  createdAt: AWSDateTime!
}

which also includes tags field

[fistofzen]

any comment?