You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 3, 2021. It is now read-only.
It seems that using nested fragments in queries results in exponential response time.
With generated query/mutation and typeDefs :
type Image {
id: ID!
url: String
}
type User {
id: ID!
displayName: String!
email: String
photo: Image @relation(name: "HAS_PHOTO", direction: "OUT")
}
when sending multiple time a query such as:
query User {
User {
...User
__typename
}
}
fragment User on User {
id
displayName
email
photo {
...Image
__typename
}
__typename
}
fragment Image on Image {
id
url
__typename
}
Response time will grow up until it crashes
Version : 2.13.0
The text was updated successfully, but these errors were encountered:
Sorry I just saw it was related to #415, and NPM version is not synced with master.
It is not happening anymore when using latest commit.
Waiting for NPM deployment :)
It seems that using nested fragments in queries results in exponential response time.
With generated query/mutation and typeDefs :
when sending multiple time a query such as:
Response time will grow up until it crashes
Version : 2.13.0
The text was updated successfully, but these errors were encountered: