Skip to content
This repository has been archived by the owner on Sep 2, 2022. It is now read-only.

Querying type for specific schema results in internal server error #718

Closed
marktani opened this issue Oct 2, 2017 · 0 comments
Closed
Assignees
Labels
Milestone

Comments

@marktani
Copy link
Contributor

marktani commented Oct 2, 2017

What is the current behavior?

Querying a type that is related to another type containing the fields a and b results in an internal server error.

Please share the relevant part of your project (GraphQL schema, functions, permissions, ...) for easier reproduction

type Post implements Node {
  id: ID! @isUnique
  comment: Comment! @relation(name: "PostComment")
  title: String!
}

type Comment implements Node {
  id: ID! @isUnique
  post: Post! @relation(name: "PostComment")
  a: Int
  b: Int
}

If applicable, share the query, mutation or subscription for reproduction

First, create a new post-comment:

mutation a {
  createPost(title: "a" comment: {a: 1, b: 3}) {
    id
  }
}

Then, query all posts:

query b {
  allPosts {
    id
    comment {
      id
    }
  }
}

You'll receive an internal server error.

What is the expected behavior?

You receive the data and no error occurs.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants