Ilya Brin

sorry to bring this up again, but do you have any other thoughts/ideas? the behavior here is definitely a bit different than handlebars.js. Here's a sample fiddle: https://jsfiddle.net/ybow1gnr/ As expected,...

FWIW, we got around this by implementing a method that converts scala collections to java collections, and make sure to always use that when providing a model/context. Implementing a resolver...

(P.S. I'm referring to this method: https://github.com/jknack/handlebars.java/blob/master/handlebars/src/main/java/com/github/jknack/handlebars/Handlebars.java#L188)

P.S. It breaks even when it's nested inside a nullable field; ```scala import pureconfig._ import pureconfig.generic.auto._ case class Foo(bar: String, baz: Option[String] = ???) case class Blah(hello: String, world: Option[Foo])...

> I wouldn't recommend setting any kind of heavy logic, particularly stateful logic, in the defaults of config classes Absolutely! For context, I was considering having some default values loaded...

That makes sense. Thanks for taking a look!