[
https://issues.apache.org/jira/browse/TAP5-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17425597#comment-17425597
]
Thiago Henrique De Paula Figueiredo commented on TAP5-2695:
-----------------------------------------------------------
The example in the ticket can now be written as
{code:java}
CoercionTuple.add(configuration, sourceType, targetType, coercion);
{code}
> Create convenience methods for contributing coercions
> -----------------------------------------------------
>
> Key: TAP5-2695
> URL: https://issues.apache.org/jira/browse/TAP5-2695
> Project: Tapestry 5
> Issue Type: Improvement
> Components: commons
> Reporter: Thiago Henrique De Paula Figueiredo
> Assignee: Thiago Henrique De Paula Figueiredo
> Priority: Minor
> Fix For: 5.8.0
>
>
> Since Tapestry 5.7.0, when contributions to TypeCoercer became mapped ones,
> they got more complicated to do.
> Example of how they were done before:
> {code:java}
> configuration.add(CoercionTuple.create(sourceType, targetType, coercion));
> {code}
> Example of how they have been done since 5.7.0:
> {code:java}
> CoercionTuple<S, T> tuple = CoercionTuple.create(sourceType, targetType,
> coercion);
> configuration.add(tuple.getKey(), tuple);
> {code}
> We should create a new method in CoercionTuple so coercion contributions can
> be again done with a single method call.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
