feat: allow deriveLinkedEntries to create multiple derived entries [] #1533
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.
Summary
deriveLinkedEntries, enabling 0..N child entries per source/locale and populating an Array<Link> field.deriveEntriesForLocale(multi-mode)derivedEntryId(deterministic IDs)publishDerived(child publishing)Description
linkContentTypewhere applicable.deriveEntryForLocale.Motivation and Context
A user asked for an easy way to convert a JSON field into many linked entries (e.g., fanning out arrays/objects into normalized child entries). This change adds multi-entry derivation so migrations can deterministically create 0..N child entries per locale and link them back, making that workflow simple and repeatable without breaking existing scripts.