Fixes a problem with Empty arrays using JSON datasources #741
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.
Previously if you had a an array of complex objects including arrays inside them, you would get a NullReferenceException if the incoming data could have any of those internal arrays be empty. With the added check, the program will correctly understand the lack of value in that property path
Eg:
in the model above, if you were to use a path like
sales.payments.value
as a totalizer, the data above would cause a NullReferenceException due to payments being an empty array, instead of the expected behavior, with the correction we get the expected result of 123