-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Range in Number Constraints is misleading #10229
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
Thanks for reporting this issue. This is indeed confusing. What if we remove Range from "Number Constraints" and move it to "Comparison Constraints". After all, Range is just "Greater than" + "Less than". |
@javiereguiluz sounds good for me created a PR #10249 |
javiereguiluz
added a commit
that referenced
this issue
Sep 4, 2018
…-schranz) This PR was squashed before being merged into the 2.8 branch (closes #10249). Discussion ---------- Move range to the comparison constraint types As the [Range](http://symfony.com/doc/3.4/reference/constraints/Range.html) constraint also work for **date** fields the section headline [Number Constraints](http://symfony.com/doc/3.4/reference/constraints.html#number-constraints) is misleading. As I first thought that the Range will work only for numbers then. fixes #10229 Commits ------- 7921ae5 Move range to the comparison constraint types
Fixed by #10249. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As the Range constraint also work for date fields the section headline Number Constraints is misleading. As I first thought that the Range will work only for numbers then.
The text was updated successfully, but these errors were encountered: