fix(api-headless-cms): skip invalid DZ values instead of throwing #4202
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.
Changes
This PR ensures that DZ field storage doesn't create a default
[]value, because it will break subsequent partial draft saving. To make this possible, we had to reduce the amount of errors being thrown by DZ field transform plugin, and instead use reasonable fallbacks. If the incoming value is not valid for storage, we simply skip it. Doing it this way ensures data consistency in the database/opensearch, and also allows us to save partial entries, where a DZ field can benullorundefined.How Has This Been Tested?
Manually, and Jest tests.