On Thu, Feb 23, 2017 at 12:31 AM, Daniel Dekany <ddek...@freemail.hu> wrote:
> Thursday, February 23, 2017, 12:22:52 AM, Woonsan Ko wrote:
>
>> On Wed, Feb 22, 2017 at 4:06 AM, Daniel Dekany <ddek...@freemail.hu> wrote:
>>> I would like to remove these deprecated FM2 FTL constructs in FM3:
>>>
>>> - #escape, #no_escape (recently deprecated in favor of 
>>> http://freemarker.org/docs/dgui_misc_autoescaping.html)
>> I'm very fine with dropping this, but I'm just curious about a 'corner
>> case'. In the '"Markup output" values' section, it explains an
>> interesting case that the caller of a macro can decide whether or not
>> the message argument should be escaped.
>> Is there a similar way to achieve that after dropping them?
>
> You mean this:
>
>     <@infoBox "Foo & bar" />
>     <@infoBox "Foo <b>bar</b>"?no_esc />
>
>     <#macro infoBox message>
>       <div class="infoBox">
>         ${message}
>       </div>
>     </#macro>
>
> That thing works exactly because of the new escaping mechanism. It has
> nothing to do with the legacy #escape, #no_escape. So, yes, it works
> without them.

Ah, right. I confused myself with the builtin. Sorry for that and thanks!

Woonsan

>
>>> - .template_name in favor of .current_template_name (there's also 
>>> .main_template_name)
>> +1
>>
>>> - http://freemarker.org/docs/ref_depr_numerical_interpolation.html
>> +1
>>
>>> - http://freemarker.org/docs/ref_depr_directive.html
>> +1
>>
>>> - http://freemarker.org/docs/ref_depr_builtin.html
>> +1
>>
>> Regards,
>>
>> Woonsan
>>
>>>
>>> Any thoughts?
>>>
>>> Some other changes were agreed upon earlier (but weren't implemented yet):
>>>
>>> - Remove tag syntax autodetection (<#> VS [#]). Use file extension (or
>>>   TemplateConfigurator-s associated otherwise) to decide the syntax.
>>>   This is to help tooling (not even the JBoss Eclipse plugin managed
>>>   to correctly deal with it).
>>>
>>> - Only keep the camel case naming convention, not only because it has
>>>   become the dominant convention nowadays, but because the data-model
>>>   uses that anyway (as it comes from Java).
>>>
>>> As you might notice, currently the focus is on removing stuff, because
>>> doing that the earliest makes refactoring less expensive.
>>>
>>> --
>>> Thanks,
>>>  Daniel Dekany
>>>
>>
>
> --
> Thanks,
>  Daniel Dekany
>

Reply via email to