If a value is queried it is possible that the value is null, '' or false.
These are all valid return values that the user might want to know about.
With the current default return value of false in the getFromNested method, a custom macro might be called with false as a value (but in this case the value does not exist). Empty strings on the other hand are never passed to the macro but the user might care about these.
To distinct these falsey values from a value that was effectifely not found, the ValueNotFound object was introduced in this commit.
If a value is queried it is possible that the value is
null
,''
orfalse
. These are all valid return values that the user might want to know about.With the current default return value of
false
in thegetFromNested
method, a custom macro might be called withfalse
as a value (but in this case the value does not exist). Empty strings on the other hand are never passed to the macro but the user might care about these.To distinct these falsey values from a value that was effectifely not found, the
ValueNotFound
object was introduced in this commit.