[
https://issues.apache.org/jira/browse/TAP5-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457602#comment-17457602
]
ASF subversion and git services commented on TAP5-2695:
-------------------------------------------------------
Commit 32353fcd3206e83c1fc56007eaacca4dc01206aa in tapestry-5's branch
refs/heads/master from Thiago H. de Paula Figueiredo
[ https://gitbox.apache.org/repos/asf?p=tapestry-5.git;h=32353fc ]
TAP5-2695: Create convenience methods for contributing coercions
> 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.20.1#820001)
