-
Notifications
You must be signed in to change notification settings - Fork 12
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
Resolver Ignores Subfield Values #16
Comments
Digging into this it looks like there are several bugs. Quick workaround would be to add an additional resolver for the resolvers: {
Query: {
search() {
// ...what you've already got here
}
},
SearchResult: {
item: ({ item }) => item
}
} I will file additional issues for the related bugs:
|
I just merged a fix for the main issue here, which was detailed in #18. Note: This fix won't help with https://github.com/Gamaranto/miragegraphqlbug due to the implementation of the |
First of all, thanks for the great library!
I was using it to mock results from a search query but I encountered what looks like a bug.
To give some context, the query that I'm trying to mock takes in a string, here is what my schema looks like:
Whatever I return as
item
from thesearch
resolver, Mirage just ignores it and returns the firstAnimal
in the database.I've put together an example repo here: https://github.com/Gamaranto/miragegraphqlbug
In the example repo, I return
null
asitem
in thesearch
resolver, but the first animal in the db is returned anyway.Thanks in advance for the help!
The text was updated successfully, but these errors were encountered: