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
Things that can do with some attention in the next minor or patch release
to mapping for Stream and Iterator do not make use of Streamable.Sized (also Sized itself it not supported out-of-the-box)
a Validation on a record component ATM always assumes the JSON is an object with the same properties but when we have case of different JSON types map to same class with a custom mapper ATM we cannot express validations on components based on case. Now, that might also be too complicated for a clear support as there are many ways of mapping. But, if to would integrate nicer with validation the validation could maybe occur within the to implementation and still contribute to a "outer" validation context?
@Validation needs some extension to customize the error message (e.g. add custom template and codes). Likely it makes sense to add another annotation that bundles all attributes around customization of errors
Things that can do with some attention in the next minor or patch release
tomapping forStreamandIteratordo not make use ofStreamable.Sized(alsoSizeditself it not supported out-of-the-box)Validationon arecordcomponent ATM always assumes the JSON is an object with the same properties but when we have case of different JSON types map to same class with a custom mapper ATM we cannot express validations on components based on case. Now, that might also be too complicated for a clear support as there are many ways of mapping. But, iftowould integrate nicer with validation the validation could maybe occur within thetoimplementation and still contribute to a "outer" validation context?@Validationneeds some extension to customize the error message (e.g. add custom template and codes). Likely it makes sense to add another annotation that bundles all attributes around customization of errors