Not all errors added when using same code on multiple fields about errors-spring-boot-starter HOT 4 CLOSED

Ok, great that you are open to this. Ideally, if there is only a single error message for a single annotation, it would be great if we could just define this in a central way, so that I can skip repeating the message = PROPERTY_SHOULD_NOT_BE_EMPTY argument for each @NotEmpty annotation. (Adding it to have a specific error message as an override should remain possible of course).

from errors-spring-boot-starter.

@wimdeblauwe That's right. We've designed this small library to have one error code for each error case. That's why we maintain the error codes inside an instance of a Set.
Anyway, we could evaluate the possibility of this feature to 1.5 release. For example, we can report one error code along with more than one argument describing the related fields.

from errors-spring-boot-starter.

Issue can be closed as I wrote my own library -> https://github.com/wimdeblauwe/error-handling-spring-boot-starter

from errors-spring-boot-starter.

Would it be possible to reopen this issue?

I came accross it recently and, even though I technically can declare a message by error case, it would make much more sense to support multiple error messages for one error type.

This is a little frustrating to see that #105 seems to tick all the boxes but hasn't been merged yet 😞

from errors-spring-boot-starter.