[TAP5-2651] TypeCoercer should favor exact match coercions over intermediate ones

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 5.6.2, 5.7.0
• Component/s: tapestry-ioc
• Assignee: Thiago Henrique De Paula Figueiredo
• Reporter: Thiago Henrique De Paula Figueiredo
• Created: 06/Dec/20 13:48
• Updated: 11/Feb/21 23:52
• Resolved: 11/Feb/21 22:11

Description

While checking why the TAP5-2645 patch had a failing test, 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.