feat(app-headless-cms): add support for nested dynamic zones and ref fields #3471
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
Pavel910
changed the title
brunozoric
approved these changes
Aug 28, 2023
# Conflicts: # packages/api-headless-cms/src/graphqlFields/dynamicZone/dynamicZoneStorage.ts # packages/app-headless-cms/src/admin/components/ContentEntryForm/useContentEntryForm.ts
brunozoric
approved these changes
Aug 29, 2023
brunozoric
pushed a commit
that referenced
this pull request
Oct 10, 2023
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.
Changes
This PR unlocks the ability to nest dynamic zone fields within object fields, within other dynamic zones, and also have ref fields within dynamic zones. Filtering of content entries within dynamic zones is still not possible.
This PR also improves the performance of reference field mapping which is executed during
createandupdateCRUD operations.Other changes:
prepareFormDatato@webiny/app-headless-cms-common, as it is being used in recursive functionscreateFieldsListto@webiny/app-headless-cms-common, as it is being used in recursive functions_empty: Stringfield, until some user-defined fields are added to the object. The same thing applies to empty dynamic zone templates.This is an example of what you can now do in your content models:
How Has This Been Tested?
Jest tests on the API side, and manually on the client side.