Hello django-developers@, 

On more than one project, I find myself implementing the same feature over
and over again. It's not a rare case scenario, for instance: it's common
that invoices have a date that belongs to the past or the present time, but
not the future.

Seeing that we have django.core.validators.MinValueValidator and
django.core.validators.MaxValueValidator, I propose the following:

* django.core.validators.DateIsPresent
* django.core.validators.DateIsPresentOrPast
* django.core.validators.DateIsPresentOrFuture
* django.core.validators.DateIsFuture

This way, one may easily use them at models.py just like MinValueValidator
and MaxValueValidator.

The code would be really simple, I have them -differently- implemented at:
https://github.com/heimdalerp/heimdalerp/blob/master/common/validators.py

Please, let me know if there's already an easier way to do this with
current Django, or if this belongs to a custom app instead.

If it is ok to add this feature to Django, I can gladly take care of it.

Thanks in advance. 

-- 
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/D6FE121C-FCA4-422C-8AF6-1E5BD87B091A%40yahoo.com.
For more options, visit https://groups.google.com/d/optout.
  • ... 'Mariano Baragiola' via Django developers (Contributions to Django itself)
    • ... Tim Graham
      • ... Ares Ou
      • ... Aymeric Augustin
    • ... Jani Tiainen
      • ... Josh Smeaton

Reply via email to