Paweł Adamczak

I think both `DateField` and `DatetimeField` really should be supported out of the box. I ended up implementing my own that just call `.isoformat()` - if you think that's good...

Yeah, it probably changed with the release of ~~Bootstrap 4~~ Font Awesome 5. Thanks for reporting, I'll try to take a look and release a fixed version.

Thanks for reporting, I'll try to find some time for the Font Awesome 5 compatibility in the next few days to fix both this and #10 and do a release....

@johnsensible would it be possible to get this reviewed/merged?

We just encountered this in our project as well. I'm wondering what's the potential solution - could we use one `filter()` call with all `kwargs` instead of one `filter()` call...

> @pawelad That could help, but you need a custom filter method for that 🙂 You may found this article useful - [hacksoft.io/django-filter-chaining](https://hacksoft.io/django-filter-chaining/) I don't think a custom filter method...

Related to #103, but I'd still vote to remove the `

Still here in 6.2.

This would be great - ideally, `v1` should point to the latest `v1.X.Y` release (currently it's `v1.4.0`), which I think is the de-facto standard with GitHub Actions (i.e. https://github.com/actions/checkout/tags).

GitHub docs don't mention any 'official way' and the two GitHub-owned actions I checked (the ones I use the most often) use two (slightly) different approaches... https://github.com/actions/checkout/blob/main/.github/workflows/update-main-version.yml https://github.com/actions/setup-python/blob/main/.github/workflows/release-new-action-version.yml