render back unresolved tokens

[marius-diumia]

This change allow to render back tokens which are unresolved.

Default behaviour is:

• context key = "resolved"
• template this is {{ key }} but this is {{ missing }}
• with output this is resolved but this is

Enabling configuration .withRenderBackUnknownTokens(true) the behaviour is:

• context key = "resolved"
• template this is {{ key }} but this is {{ missing }}
• with output this is resolved but this is {{ missing }}

[marius-diumia]

Hi @jasmith-hs I want to ask you if there is a change to merge my PR in one of the next releases.
Currently I'm using the workaround as you suggested in the issue #1046. But it doesn't cover all the use cases which I need. Problem with this is that it doesn't support filters. I need to be able to maintain the variable not resolved, but in the same time to be able to assign a default. Just updated the unit test which show that use case.
Thanks

[jasmith-hs]

@marius-diumia would you be able change this to use the new Features way of adding flags: #1066, and then I can merge it in for the next release

[abarrafo]

Just opened this pr #1150 leveraging Features..

[abarrafo]

@marius-diumia you can close this out now. Have a look in the test in PR: #1150 for usage. @jasmith-hs what is your release lifecycle? When would we expect this to be in maven-central? Thanks!

[marius-diumia]

resolved by PR #1150