[jira] [Created] (TAP5-2651) TypeCoercer should favor exact match coercions over intermediate ones

["Thiago Henrique De Paula Figueiredo (Jira)" <ji...@apache.org>]

Thiago Henrique De Paula Figueiredo created TAP5-2651:
---------------------------------------------------------

             Summary: 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


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)