On Mon, Jun 7, 2021 at 5:38 AM Numa Schmeder wrote:
> Hi Thiago,
>
Hello!
> Thank you for your feedback, yes indeed, I have checked the code of the
> property binding and the antler syntax.
> Indeed it compiles byte code based on real method signature, so you can’t
> be to generic or it won’t
Hi Thiago,
Thank you for your feedback, yes indeed, I have checked the code of the
property binding and the antler syntax.
Indeed it compiles byte code based on real method signature, so you can’t be to
generic or it won’t find the method you have written.
I will look into chenille kit for
On Wed, May 26, 2021 at 7:00 AM Numa Schmeder wrote:
> Hello,
>
Hello!
> It seems method with varargs doesn’t work with property expression.
> If I put the following property expression, I get an error: Message
> doesn’t have a public “format" method.
> ${messages.format('priceFromPerGuest',
Hi,
Thank you. I know, I realized I made a typo. It should be:
@Property
Object tempValue
${tempValue.getName(locale)} - ${getPopulation(tempValue)}
I think var prefix is a great addition, but it should be able to use var in
property expression, and not only as single read write
We never really use much of the expression language, so I can't comment on
that.
This is just a comment on the last example: I'm not sure that you need a
@Property when using the "var:" prefix (if you have a backing property it
ought to be a "prop:" binding, as far as I understand)
--
Chris
Hello,
It seems method with varargs doesn’t work with property expression.
If I put the following property expression, I get an error: Message doesn’t
have a public “format" method.
${messages.format('priceFromPerGuest', travelMinPricePerGuest,
displayedCurrency)}
But If I write it as follow
