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

Error keeps appearing, preventing me from syncing with Figma or updating forms #1105

Open
4 tasks done
Bryson14 opened this issue Feb 24, 2024 · 2 comments
Open
4 tasks done
Labels
pending-triage An issue that is pending triage

Comments

@Bryson14
Copy link

Before creating a new issue, please confirm:

On which framework/platform are you having an issue?

React

Which UI component?

Other

How is your app built?

cra

What browsers are you seeing the problem on?

Chrome

Which region are you seeing the problem in?

us-east-1

Please describe your bug.

I have seen this error appear that says "failed to save The number of resources passed must be greater than 0 and less than 100". this appears usually when I'm configuring a form or imported component from Figma. At the top, instead of saying "changes saved", it shows this error. Now I can't import from Figma without getting this error.
Screenshot from 2024-02-24 11-14-39
importing

What's the expected behaviour?

this should not appear, or point to a previous form configuration where the problem is originating from.

Help us reproduce the bug!

I'm not sure how to

Code Snippet

// Put your code below this line.

Console log output

No response

Additional information and screenshots

No response

@github-actions github-actions bot added the pending-triage An issue that is pending triage label Feb 24, 2024
@Bryson14
Copy link
Author

i recently updated my graphql schema to

type GroupClass @model @auth(rules: [{allow: public, operations: [read]}, {allow: groups, groups: ["admins"], operations: [read, create, update, delete]}]) {
  id: ID!
  title: String!
  subtitle: String
  description: String
  sessions: [GroupClassSession] @hasMany(indexName: "byGroupClass", fields: ["id"]) # many a connection to the GroupClassSession model, but also using the GSI to query by the GroupClass id
  isActive: ClassStatus! @index(name: "byStatus")
  tags: [String!]
}

type GroupClassSession @model @auth(rules: [{allow: public, operations: [read]}, {allow: groups, groups: ["admins"], operations: [read, create, update, delete]}]) {
  id: ID!
  title: String!
  description: String
  groupClassId: ID! @index(name: "byGroupClass", queryField: "groupClassSessionsByGroupClass", sortKeyFields: "startDateTime")
  tutorId: ID! @index(name: "byTutor", queryField: "groupClassSessionsByTutor", sortKeyFields: "startDateTime")
  Tutor: Tutor! @hasOne(fields: ["tutorId"])
  startDateTime: AWSDateTime!
  tutorPaid: Boolean!
  tutorPayAmount: Float
  paymentNotes: String
  duration: Int!
  fileKeys: [String]
  meetingUrl: AWSURL
  meetingInstructions: String
  canSignUp: ClassStatus! @index(name: "byStatus")
  tags: [String!]
}

type GroupClassSessionBooking @model @auth(rules: [{allow: private, operations: [read]}, {allow: groups, groups: ["admins"], operations: [read, create, update, delete]}]) {
  id: ID!
  groupClassSessionId: ID! @index(name: "byGroupClassSession", queryField: "groupClassSessionBookingsByGroupClassSession")
  GroupClassSession: GroupClassSession! @hasOne(fields: ["groupClassSessionId"])
  clientId: ID! @index(name: "byClient", queryField: "groupClassSessionBookingsByClient", sortKeyFields: ["signUpDateTime", "clientPaid"])
  Client: Client @hasOne(fields: ["clientId"])
  studentId: ID! @index(name: "byStudent", queryField: "groupClassSessionBookingsByStudent", sortKeyFields: ["signUpDateTime", "clientPaid"])
  Student: Student @hasOne(fields: ["studentId"])
  clientPaid: PaymentStatus! @index(name: "byPaymentStatus")
  transactionId: String
  paymentNotes: String
  signUpDateTime: AWSDateTime!
  logHistory: [String!]
}

Maybe is have to do with the [String!] data type

@hbuchel
Copy link

hbuchel commented Feb 26, 2024

Hi @Bryson14 this looks like an error specific to Studio so I'm transferring your issue over to their repo.

@hbuchel hbuchel transferred this issue from aws-amplify/amplify-ui Feb 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pending-triage An issue that is pending triage
Projects
None yet
Development

No branches or pull requests

2 participants