[TAMAYA-128] Adding ConversionContext to converter params

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Implemented
• Affects Version/s: 0.1-incubating
• Fix Version/s: 0.2-incubating
• Component/s: API
• Assignee: Anatole Tresch
• Reporter: Anatole Tresch
• Created: 29/Oct/15 10:31
• Updated: 30/Oct/15 10:04
• Resolved: 30/Oct/15 10:04

Description

For passing metadata to a PropertyConverter more arguments are needed then only the simple String input value. Therefore an additional ConversionContext is passed with the following data:

• the requested key
• the requested target type
• the base configuration
• the injected field or method (optional).
• a (mutable) list of supported formats as Strings

The ladder also provides an elegant way to enable converters to dynamically register their supported formats, making them available for improved user feedback on the currently supported formats for a type. Nevertheless the PropertyConverter interface can stay functional.

Unfortunately this change breaks the current PropertyConverter SPI, but extending the ConversionContext should be possible when needed in the future without breaking the API again.

Issue Links

• contains: TAMAYA-67 PropertyConverter: add info for supported formats