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/02/11 22:12:00 UTC
[jira] [Closed] (TAP5-2651) TypeCoercer should favor exact match
coercions over intermediate ones
[ https://issues.apache.org/jira/browse/TAP5-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thiago Henrique De Paula Figueiredo closed TAP5-2651.
-----------------------------------------------------
Resolution: Fixed
> TypeCoercer should favor exact match coercions over intermediate ones
> ---------------------------------------------------------------------
>
> Key: TAP5-2651
> URL: https://issues.apache.org/jira/browse/TAP5-2651
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-ioc
> Reporter: Thiago Henrique De Paula Figueiredo
> Assignee: Thiago Henrique De Paula Figueiredo
> Priority: Major
> Fix For: 5.6.2, 5.7.0
>
>
> While checking why the TAP5-2645 patch had a [failing test|https://ci-builds.apache.org/job/Tapestry/job/tapestry-trunk-freestyle/47/testReport/ioc.specs/TypeCoercerSpec/coerce_java_lang_Integer_2020_to_java_time_Year_should_be_2020/], I noticed I was wrong about an assumption I made about TypeCoercer: it doesn't favor exact match coercions (i.e. coercions with the exact same source and target classes) over other ones, leaving the possibility of an intermediate (i.e. non-direct) one to be picked up even when an exact match one exists.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Re: [jira] [Closed] (TAP5-2651) TypeCoercer should favor exact match
coercions over intermediate ones
Posted by Philippe Siquin <ph...@informatique.gov.pf>.
unsubscribe
On 11/02/2021 12:12, Thiago Henrique De Paula Figueiredo (Jira) wrote:
> [ https://issues.apache.org/jira/browse/TAP5-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Thiago Henrique De Paula Figueiredo closed TAP5-2651.
> -----------------------------------------------------
> Resolution: Fixed
>
>> TypeCoercer should favor exact match coercions over intermediate ones
>> ---------------------------------------------------------------------
>>
>> Key: TAP5-2651
>> URL: https://issues.apache.org/jira/browse/TAP5-2651
>> Project: Tapestry 5
>> Issue Type: Improvement
>> Components: tapestry-ioc
>> Reporter: Thiago Henrique De Paula Figueiredo
>> Assignee: Thiago Henrique De Paula Figueiredo
>> Priority: Major
>> Fix For: 5.6.2, 5.7.0
>>
>>
>> While checking why the TAP5-2645 patch had a [failing test|https://ci-builds.apache.org/job/Tapestry/job/tapestry-trunk-freestyle/47/testReport/ioc.specs/TypeCoercerSpec/coerce_java_lang_Integer_2020_to_java_time_Year_should_be_2020/], I noticed I was wrong about an assumption I made about TypeCoercer: it doesn't favor exact match coercions (i.e. coercions with the exact same source and target classes) over other ones, leaving the possibility of an intermediate (i.e. non-direct) one to be picked up even when an exact match one exists.
>
>
> --
> This message was sent by Atlassian Jira
> (v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org