Guys,
I'm kinda disappointed here, I came here with a valid issue and no one seems to
see a problem here, I don't want to fix it in my project we are already using
ifNotNull component I just want a syntax option improvement which will avoid
some behavior/performace issues.
It could pretty much confuse beginners because if someone will write:
<t:if test="user.limit">
it will return false even if limit is a zero, it could be an expected behaviour
but if limit is valid/is set only if there is not null value you are giving no
quick option here.
I don't want to change default Object - > boolean coercion or somekind of
PropertyConduitSource hack, it will break stuff and just admit nobody will
change it in the framework so don't argue that it could be fixed here.
I'm surprised that you didn't discover that kind of problem in big projects
with complicated view logic, even Howard suggested to use an approach which I
would never suggest in our team, toString is getting called on unknown object
to check if it isn't a "false" is a little bit to much of Tapestry magic and I
don't think that Tapestry should force developers to use the only one way.
Thanks,
Denis
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
