I have a handlebars template which is filled in by an API query that can return null field values.
Is there an expectation on how nulls should be resolved?
In both MapValueResolver and MemberValueResolver, a null value gets treated as unresolved and falls through to the next resolver instead of checking to see whether the key is present in the object and returning null instead of UNRESOLVED.
The only reason I noticed this is we are in an environment with multiple class loaders and JavaBeanValueResolver/MemberValueResolver setAccessible() was throwing an exception for an object which was a simple map.
I have a handlebars template which is filled in by an API query that can return null field values.
Is there an expectation on how nulls should be resolved?
In both MapValueResolver and MemberValueResolver, a null value gets treated as unresolved and falls through to the next resolver instead of checking to see whether the key is present in the object and returning null instead of UNRESOLVED.
The only reason I noticed this is we are in an environment with multiple class loaders and JavaBeanValueResolver/MemberValueResolver setAccessible() was throwing an exception for an object which was a simple map.