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

Schema problem #17

Open
sarbhsinghal opened this issue Mar 19, 2019 · 3 comments
Open

Schema problem #17

sarbhsinghal opened this issue Mar 19, 2019 · 3 comments

Comments

@sarbhsinghal
Copy link

When we print the schema by new SchemaPrinter().print(schema) , then all the mutation types are also coming in QUERY_ROOT ?

@kaqqao
Copy link
Member

kaqqao commented Mar 19, 2019

I don't understand what you mean by mutation types? If mutations (fields representing mutations) are listed under query root, you likely have a malformed schema. Inspect the schema you're getting.
What SPQR version are you using? Asking because QUERY_ROOT has been changed very long ago.

@sarbhsinghal
Copy link
Author

type MUTATION_ROOT {
logout : Boolean
signinUser(auth : AuthDataInput) : SignInPayload
deleteUser : Boolean
updateUser(lastName : String, firstName : String, password : String, gender : String, email : String) : User
createUser(lastName : String, firstName : String, password : String, gender : String, email : String) : User
}

type QUERY_ROOT {
getAllUsers : [User]
logout : Boolean
signinUser(auth : AuthDataInput) : SignInPayload
deleteUser : Boolean
updateUser(lastName : String, firstName : String, password : String, gender : String, email : String) : User
user(email : String) : User
createUser(lastName : String, firstName : String, password : String, gender : String, email : String) : User
}

I am getting this on doing SchemaPrinter().print(schema). It has all the mutations as query type also.

io.leangen.graphql spqr 0.9.1

I am using 0.9.1 version of spqr wth java 1.8.

@kaqqao
Copy link
Member

kaqqao commented Mar 26, 2019

Unless you show how you're building the schema, there's no way to tell what happens. I don't have a crystal ball.
Please provide a minimal example displaying the unexpected behavior.

Also, 0.9.1 is a 2 year old version of a constantly evolving project. Please upgrade to the latest (0.9.9 at the time of writing).

Finally, this is the samples project and unless your problem is with a sample this is the wrong place to open an issue.

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

No branches or pull requests

2 participants