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
Currently, the @defaultOption annotation is sloppy at best for providing non-primitive default objects for configuration values. I propose the use (or at least the option to use) default methods to return objects as default values. This is supplemented by the fact that customized serializers already exist in DazzleConf and more importantly already support deserialization of objects. The only issue being the use of default methods as helper methods in configuration classes, for which i propose an annotation that would allow a default method to be ignored, or a boolean that controls configuration reading accepting default methods as default values.
The text was updated successfully, but these errors were encountered:
Currently, the @defaultOption annotation is sloppy at best for providing non-primitive default objects for configuration values. I propose the use (or at least the option to use) default methods to return objects as default values. This is supplemented by the fact that customized serializers already exist in DazzleConf and more importantly already support deserialization of objects. The only issue being the use of default methods as helper methods in configuration classes, for which i propose an annotation that would allow a default method to be ignored, or a boolean that controls configuration reading accepting default methods as default values.
The text was updated successfully, but these errors were encountered: