fix: allow self referencing relationships when adding new collections to config #9360
+7
−1
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
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?
Unable to add collections to the config dynamically if they reference their own collection in a relationship field.
This was discovered while working on the folder view feature which dynamically adds collections to your config if it is enabled per collection.
Why?
When
sanitizeCollectionruns, it takes the current config. If you are sanitizing a collection before adding it to the config, that collection cannot have any self referencing relationship fields on it otherwise it fails the validRelationships check.How?
Using a reducer we now initialize the validRelationships variable with the incoming collection slug.