ClassCastException if Context isn't a ContextImpl about handlebars.java HOT 5 CLOSED

I see it.

Issues #17 solve one part of the problem, but not what you're trying to do. A have one question for you:

• In your custom Context, are you dealing with the context stack? what about the rules behind the context stack? or are you just resolving the value from a field?

From my perspective, a user should never never need to create a custom Context (that is why #17 was created).

A different/safe approach will be the extend the context API with the ability to let client to resolve value and reuse all the context stack rules. This also means:

• Context will be a final class
• You can provide custom "lookup" or value resolver (method, fields, map, etc.)

What do you think?

Thanks

from handlebars.java.

It sounds good. My context implementation had way too much code copied from your ContextImpl anyway.

from handlebars.java.

fixed in 0.2.0. The jar is in maven central. I'll write the release notes later today

Oh, have a look to the README, specially the Advanced usage section

from handlebars.java.

It's perfect...

except :-) for the Context.newContext() call in DefaultOptions.apply() where I can't find a way to add the FieldValueResolver that I want. So

   {{#each users}} {{.name}} {{/each}}

works only if the User class have a getName(), not if 'name' is a field.

from handlebars.java.

good catch! All the issues are more or less related to making public "Context", I have to review Options#apply and Template#apply.

wait for the next release, everything will be working as expected!

from handlebars.java.