Adding more verbose validation error messages in case of both "min_value" and "max_value" limits are set.

[SergeyPiskunov]

Description

No global issues solved, just a tiny fix:

Imagine such a field within our API:
value = serializers.IntegerField(min_value=10, max_value=30)

Let's assume the User makes the request to our API with such a payload: {"value": 5}
The API answers: "Ensure this value is greater than or equal to 10"
User updates the payload with {"value": 50}
The API answers: "Ensure this value is less than or equal to 30"

With current fix the very first response from the API would be: "Ensure this value is in the range between 10 and 30." which is more verbose for the API users.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[auvipy]

can you please rebase? there have two more PR merged in this section very recently

[tomchristie]

There's a trade-off here. Adding a more verbose validation error message, also means that we've then got a new untranslated string across all of our supported languages.

Personally I think that REST framework is far enough along it's lifecycle that we should be deal strictly with bug fixes and keeping pace with newer Django versions.