Add removeEmpty function to allow easy removal of NULL values, empty strings, empty objects and empty arrays #759
Conversation
This file contains hidden or 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
…gs, empty objects and empty arrays
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Many schemas are configured to not allow empty objects, arrays or NULL values.
When writing JSONata scripts to generate output, it can be challenging to write conditional logic that checks whether or not deeply nested arrays/objects actually have data to generate without creating a lot of duplicate logic checks.
The removeEmpty function allows you to wrap any block of JSONata code to recursively process the results and remove empty arrays, objects, null values and optionally, empty strings.
This Pull Request contains updates to the documentation as well as a comprehensive suite of tests.
Signed-off-by: Eric Litwin [email protected]