Fixed #26834 -- Made IntegerField forward min/max validators to form …

[sgzsh269]

…field

The change forwards the user set limit values of MinValueValidator/MaxValueValidator
defined in the model IntegerField to the form field using the formfield() method.

Thanks Markus Holtermann for help with the patch.

[MarkusH]

Could you wrap this as

if2 = models.IntegerField(
    validators=[validators.MinValueValidator(10), validators.MaxValueValidator(100)]
)

please.

[MarkusH]

What happens when a field has more than one MaxValueValidator (or MinValueValidator) where the boundary values differ, e.g.

field = IntegerField(validators=[MaxValueValidator(5), MaxValueValidator(10)])

[timgraham]

I think when we talked at the sprints, you indicated there was another issue that needed to be fixed before this one. Do you have any follow up with details about that? Should we close this in the meantime?

[sgzsh269]

@timgraham yes, the issue is related to the validators property, it needs further evaluation. Haven't gotten a chance to work on it but plan to do it soon.
I think @MarkusH mentioned at the time that the fix for the validators property issue could be included in this same PR.
Should I create a separate ticket and subsequently a separate PR for the validators property issue?

[timgraham]

A separate ticket/PR is fine. Sometimes a PR will include multiple commits but separating them if they stand on their own is fine too.

[timgraham]

Closing since this isn't suitable for merge yet.

[mluszczyk]

@sgzsh269 are you still working on this? I'd like to see this feature included into Django and I'll be happy to help with this patch. Could you elaborate on the "issue related to the validators property", is there a ticket for it?