You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Thiago Henrique De Paula Figueiredo (Jira)" <ji...@apache.org> on 2021/10/07 14:18:00 UTC

[jira] [Updated] (TAP5-2695) Create convenience methods for contributing coercions

     [ https://issues.apache.org/jira/browse/TAP5-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thiago Henrique De Paula Figueiredo updated TAP5-2695:
------------------------------------------------------
    Description: 
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.



  was:
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:java}

We should create a new method in CoercionTuple so coercion contributions can be again done with a single method call.




> 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
>            Priority: Minor
>
> 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)