[
https://issues.apache.org/jira/browse/WICKET-6347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943585#comment-15943585
]
Pedro Santos commented on WICKET-6347:
--------------------------------------
Because we have another interface doing it (IModel, and I also pointed the
semantic error in Martjin's mail thread earlier today) does not actually
counter my point that it's a semantic error. But you are invited to show your
technical point instead of to plain point that are not convinced.
The alternative implementation I proposed for the components that could detach
renderers should cover your use case and adds no semantic error to the code.
> IChoiceRenderer implements IDetachable
> --------------------------------------
>
> Key: WICKET-6347
> URL: https://issues.apache.org/jira/browse/WICKET-6347
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 8.0.0-M4
> Reporter: Sven Meier
> Assignee: Sven Meier
> Priority: Trivial
>
> IChoiceRenderer (and other renderers ) don't implement IDetachable currently.
> I've came across situations where this would have been handy, and apparently
> other users would also welcome such an improvement:
>
> http://stackoverflow.com/questions/42933128/automatically-detaching-choice-renderer-in-wicket
> I've made the required changes locally and there's no negative impact as far
> as I can see.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
