[ https://issues.apache.org/jira/browse/TAP5-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17410861#comment-17410861 ]
Gamel Alomaisi commented on TAP5-2414: -------------------------------------- My name is walli > 5.4-beta-22 and mixins parameters prefix > ---------------------------------------- > > Key: TAP5-2414 > URL: https://issues.apache.org/jira/browse/TAP5-2414 > Project: Tapestry 5 > Issue Type: Wish > Components: tapestry-core > Affects Versions: 5.4 > Reporter: Julien POLLY > Priority: Minor > Labels: 54_release_prerequisite > > We recently moved to 5.4-beta-22. > We discover that it is now required to add for all mixins parameters in the > tml, the prefix of the mixin (the associated commit is > https://github.com/apache/tapestry-5/commit/1f0c7464c80e415a19825c612ca6b8139db6ba1e). > We think that it is a good thing to prevent conflict between components and > mixins. > But is it possible to provide a backward compatibility system so that we can > still use the mixin parameters without the prefix. > Otherwise we will be forced to go through all our TMLs to modify them and it > is a lot of work ! > For example, a configuration value saying if : > - the prefix is strict (only parameters with prefix are allowed) > - the prefix is optional (both syntax with and without a prefix are allowed) > - the prefix is disallowed > Thanks in advance. -- This message was sent by Atlassian Jira (v8.3.4#803005)