Extend supported data types in @Settings objects

[thomasrutger]

Currently, configuration objects can be injected directly using the @Configuration, @Settings and @Setting annotations. This helps a lot with basic configuration. However, currently, only basic data types such as Integer, String, etc. are supported. Anything else has to be manually mapped. It would be very nice if more advanced objects such as List would also be supported (e.g. by using the bracket notation in the properties). Are there any concrete plans to extend the current configuration injection logic?

[jimmarino]

Currently, configuration objects can be injected directly using the @Configuration, @Settings and @Setting annotations. This helps a lot with basic configuration. However, currently, only basic data types such as Integer, String, etc. are supported. Anything else has to be manually mapped. It would be very nice if more advanced objects such as List would also be supported (e.g. by using the bracket notation in the properties). Are there any concrete plans to extend the current configuration injection logic?

Hi,

No, as doing so will quickly require a full-blown databinding solution. If you want this type of behavior, you could create a custom config extension that interprets an entry as a reference to another source that can then be read, parsed, and bound to the Java type system.