-
Notifications
You must be signed in to change notification settings - Fork 64
Support ObjectID in findByFields() #75
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
Merged
lorensr
merged 1 commit into
GraphQLGuide:master
from
tubbo:support-objectids-in-any-find-by-fields
Aug 21, 2021
Merged
Support ObjectID in findByFields() #75
lorensr
merged 1 commit into
GraphQLGuide:master
from
tubbo:support-objectids-in-any-find-by-fields
Aug 21, 2021
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The `findByFields()` method could not find documents by a given ObjectID because the `stringToId()` function was only being run when querying for a field named `_id`. Since any MongoDB field could in theory contain an ObjectID, this broke queries looking for ObjectIDs in arbitrary fields. To resolve this, remove the condition testing for the field name of `_id` and run `stringToId()` on all values. This will validate whether a given String value is actually in the ObjectID format before proceeding, so it seems safe to apply everywhere. Fixes GraphQLGuide#65
Thanks for the fix! Published in 0.4.7
You upgraded from 0.4.6? How's https://github.com/GraphQLGuide/apollo-datasource-mongodb/releases/tag/0.5.0 ?
@lorensr yes, I went from 0.4.6 to 0.4.7 - I can give 0.5.0 a whirl at some point this weekend. Thanks! 😸
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
findByFields()method could not find documents by a given ObjectID because thestringToId()function was only being run when querying for a field named_id. Since any MongoDB field could in theory contain an ObjectID, this broke queries looking for ObjectIDs in arbitrary fields. To resolve this, remove the condition testing for the field name of_idand runstringToId()on all values. This will validate whether a given String value is actually in the ObjectID format before proceeding, so it seems safe to apply everywhere.The tests passed locally when I changed this implementation, which means there is probably something wrong with the mocks in the
cache.test.js...might be something to look into. This at least confirmed my belief as I was observing very different behavior in the real world than what the tests would have suggested.Fixes #65