-
Notifications
You must be signed in to change notification settings - Fork 472
Add @DecimalMin and @DecimalMax for Hal+Forms Property Metadata #1557
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Since |
This feature would possibly require the |
Add support for decimal-based type validation constraints.
Add support for decimal-based type validation constraints.
Add support for decimal-based type validation constraints.
Add support for decimal-based type validation constraints.
Would be wonderful to also update the reference documentation. |
@talentedasian – Would you mind stopping to mess with the tickets and pull requests? I'm getting lost in all the notifications for this ticket. Please let us take care of that, thanks! Reopening as there's pending work in an issue branch. |
Add support for decimal-based type validation constraints.
Add support for decimal-based type validation constraints.
Add support for decimal-based type validation constraints.
Add support for decimal-based type validation constraints.
Add support for decimal-based type validation constraints.
Add support for decimal-based type validation constraints.
That's in place with the current snapshots for inclusion in 1.4 M1. |
In the current Spring Hateoas, it is not possible to add a limit for decimal values. It would be useful for fields accepting decimal values.
@DecimalMin/@DecimalMax
currently does not work and is only limited to having the@Min/@Max
annotations.The text was updated successfully, but these errors were encountered: