> On 17 Mar 2021, at 15:34, Jacob Rief <jacob.r...@gmail.com> wrote: > > But FloatField also offers a min_value and max_value. When rendered as a > widget, they are used as attributes min and max in their input > field. In addition to that, the field value is validated against a value in > that range. To be consistent, the same should apply to the step value. > This would furthermore allow the field to validate against a multiple of > that step value. Such a feature currently has to be implemented on the > project level.
If we’re happy to add that extra to forms.FloatField then it would alleviate my concern about a pass-through parameter. (At least the field would be **doing** something with it.) (I don’t object if everyone is keen.) C. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/8A007E70-C106-4705-B33C-ED8269161546%40gmail.com.
