ljacqu
ljacqu
@Prof-Bloodstone Just to mention that I've now released 1.2.0. I was hoping to do it earlier in the week but now is better than never I guess. :)
Seems impossible to do currently: - `@NotNull` and `@Nullable` have `SOURCE` retention, so need to use org.reflections or javassist to pick out the values - org.reflections has no way of...
Creating a child interface to `SettingsHolder` would allow to mark classes with property values on fields directly. If the class has instance variables we can check for non-null default values...
Unordered thoughts: Maybe by unifying the bean mapper types and the property types into one interface, we could still allow the current style of Property fields for whoever like this...
Distantly related to #197 which is about a configurable "dev mode" where more exceptions are thrown. Maybe "dev mode" should also mostly log a lot of stuff :smile:
Distantly relates to #64
This is a great request! Do you have a use case and/or a preference? I guess java properties would be more interesting than json because it allows comments
Also as addendum I‘m currently refactoring the whole project so it might take a while until I‘m able to implement a new type. But ConfigMe is definitely structured to support...
Duplicate of #316
Thank you for the ping! Relates to https://github.com/ljacqu/DependencyInjector/issues/52, which I forgot about