Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Q] resolvers & null values #1141

Open
hancockks opened this issue Aug 28, 2024 · 0 comments
Open

[Q] resolvers & null values #1141

hancockks opened this issue Aug 28, 2024 · 0 comments

Comments

@hancockks
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant