Hi, I noticed that the constructor for EnumValueEncoder was changed in T5.3 to address some issues. Although more flexible, It feels like this is something that should be transparently handled by the framework. We now need more code (i.e inject TypeCoercer) to use this feature. Anyway, I think this change needs to be added to the breaking changes section in the release notes.
My 2c. /Serge -- View this message in context: http://tapestry-developers.221625.n2.nabble.com/EnumValueEncoder-in-T5-3-tp6962704p6962704.html Sent from the Tapestry Developers mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
