feat: Return null on accessing a non-existing property #709
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
Change the expected behavior if an expression access a non-existing property. Instead of failing the evaluation, it should return null.
Change the behavior for accessing a non-existing property. Instead of failing the evaluation, it returns null instead. A failure with a descriptive message is reported. This change is aligned with the DMN specification and the new direction to be more null-friendly.
|
@nicpuppa here is a small PR for you. It is related to the other topics recently. Please have a look in the next few days. Thank you! 🍪 |
nicpuppa
approved these changes
Sep 11, 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.
Description
Change the behavior for accessing a non-existing property. Instead of failing the evaluation, it returns
null. A failure with a descriptive message is reported.This change is aligned with the DMN specification and the new direction to be more null-friendly.
Related issues
closes #707