#24170: DateTimeRangeField: widget doesn't implement decompress()
-------------------------------------+-------------------------------------
Reporter: joelburton | Owner: ngzhian
Type: Uncategorized | Status: assigned
Component: Database layer | Version: 1.8alpha1
(models, ORM) |
Severity: Normal | Resolution:
Keywords: DateTimeRangeField | Triage Stage: Accepted
decompress |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by ngzhian):
Replying to [comment:3 charettes]:
> I think creating a single `RangeWidget(widgets.Widget)` class in a new
`widgets` module that implements the decompress method should do.
Implemented it and submitted a PR, it's lacking test though, I'm not too
sure how to test it. Will creating a field of each type
`IntegerRangeField`, `FloatRangeField`, `DateTimeRangeField`, and
`DateRangeField` and asserting `self.widget.decompress()` be sufficient?
--
Ticket URL: <https://code.djangoproject.com/ticket/24170#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.58ef19bf3b1c5d25deeeb9550ae3c98c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
