You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a user of the configuration API and/or injection mechanisms, I expect there to be a range of default value type conversions so that I can have configuration values of common JDK value types without having to explicitly enable or implement those conversions.
Source: #27 (comment)
The text was updated successfully, but these errors were encountered:
As written, this would require reflection. I think we should not mandate reflection as part of this specification.
If we want to support valueOf or parse for ANY type, we would need to use reflection at runtime, which is against trends (and peformance).
If we still want to have support for additional types, we would need to add some way to mark such types, so they can be processed at build time.
As a user of the configuration API and/or injection mechanisms, I expect there to be a range of default value type conversions so that I can have configuration values of common JDK value types without having to explicitly enable or implement those conversions.
Source: #27 (comment)
The text was updated successfully, but these errors were encountered: