v4.3.0 (2024-09-10)
Chore
- chore(ci): upgrade python-semantic-release to v9.8.8 (#176)
There have been a lot of releases since v8.0.8
https://github.com/python-semantic-release/python-semantic-release/blob/master/CHANGELOG.md#v808-2023-08-26
The breaking change was dropping Python 3.7. While this project supports
3.7... that will change the next opportunity (50a03af)
-
chore: update Django/Python test matrix and add classifier for py3.12 (#171) (
ad3b898) -
chore: add Django v5 to CI matrix (#166)
https://docs.djangoproject.com/en/5.0/releases/5.0/ (b63aac1)
Documentation
- docs: add Django Modal Actions as a similar package (#173)
Adding new Django Modal Actions package
Deleting Django Object Actions which hasn't had a commit in 3 years (813687e)
Feature
- feat: add a way to make a POST only action (#174)
Followup to #168 to get CI to pass again, documents how to make a POST
only action, and adds some test coverage.
There are still a few cleanup issues but this should get things moving
on POST only actions again. (494d581)
Style
Unknown
- wip to select GET or POST for actions (#168)
Another try at enforcing POST actions. This change is more gradual than
#149 - when library user doesn't change default options the behavior is
exactly the same as before the change, that is:
- Action buttons send GET requests
- Action handlers accept GET and POST requests
However, user can change this behavior using methods and button_type
kwargs. For example @action(methods=['POST'], button_type='form')
results in
- Action button sends POST requests
- Action handler accepts only POST request
Unfortunately I have this tested only within my project. Also the docs
are missing.
And one more thing - I think it is better to use <input type="submit">
instead of js to submit the form. This js is need to make the buttons
look the same in both versions. With proper CSS (that is beyond my
ability to write ;) ) js is avoidable and we could be using pretty
semantic html submit button. I took the form button template from #149. (1274ae7)