fix(db-mongodb): ensure relationships are stored in ObjectID
#8932
Conversation
This file contains 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
DanRibbens
requested changes
Oct 30, 2024
…ested-to-arrays-and-blocks-relationship-fields-in-ObjectID-with-the-mongodb-adapter
DanRibbens
approved these changes
Oct 30, 2024
DanRibbens
deleted the
fix/store-nested-to-arrays-and-blocks-relationship-fields-in-ObjectID-with-the-mongodb-adapter
branch
|
🚀 This is included in version v3.0.0-beta.121 |
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.
What?
Since the join field, we do store relationship fields values in
ObjectID. This wasn't true if the field is nested to an array / blocks.Why?
All relationship fields values should be stored in
ObjectID.How?
Fixes arrays / blocks handling in the
traverseFields.tsfunction. Before it didn't run for them.