-
Notifications
You must be signed in to change notification settings - Fork 5
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
Querying a filtered collection breaks on updated documents #379
Comments
I added one test which passes: 8cd21bd Maybe we need to add filtering/ordering or only update one of the documents in the collection. |
Interesting, I'll share later which query failed. Might also be a nested relation 🤔 |
Just noticed that your test doesn't touch the GraphQL bit, but the case we looked at failed in the resolvers logic, maybe the issue is there? |
Yeh, should check there as well. There's not a lot (in terms of query logic) going on in the GraphQL though, so my instinct is that we can observe it here. Might be wrong about that of course. |
I've added more information now, we're getting closer:
Don't think that's the case, since this query does not contain any nesting (the other one did).
Definitely breaking when adding filtering, don't think its about ordering or that it's only one document. |
The following query breaks aquadoggo after
eth_public_key
field got updated:.. with the following error:
The query works when removing either the
filter
or theeth_public_key
field:filter
+eth_public_key
= 💥eth_public_key
only = ✅filter
only = ✅Probably related: #356
The text was updated successfully, but these errors were encountered: