Havoc Pennington

At the point you're doing the getInt the 20 has already been discarded unfortunately. Since it would be global to the config not specific to this path, I'm not sure...

you can put `${SOME_ENV_VAR_NAME}` in your application.conf if you want to just have certain fields that are set via env var, that's the typical use. If you want to be...

there isn't a current feature for those things

It seems reasonable to me I guess, open to other people's takes

At first glance, I agree, this should not be trying to resolve (since it's overridden and there was nothing forcing it to resolve). The way I'd approach this bug would...

This isn't a backward-compatible change, so in some sense discussing the merits of it is academic, but the reason we didn't do this was to keep the existing spec for...

So, I didn't try it yet, but this may not handle something like: ``` containsundefined = { bar : ${undefined} } foo = "" foo = ${containsundefined} foo = {...

I played with it some and the real fix here gets extremely complicated to understand, though I'm not sure it would be a large patch once understood. It may be...

The caveat here is that conversion to Properties is lossy, so some type information and even values can be lost. That said I'd probably do this as some sort of...

thanks for the links! Just thinking the details here maybe depend on the use case a little. for example should all values be converted to strings? if a value can't...