Open phillxnet opened 10 months ago
This issue depends on: "Update Django to next LTS" #2734
Context: https://django-htmx.readthedocs.io/en/latest/changelog.html#id9
1.11.0 (2022-05-10) Drop support for Django 2.2, 3.0, and 3.1.
Re:
This issue depends on: "Update Django to next LTS" #2734
With a follow-up further Django update via PR: "Update Django to latest 4.2 LTS #2750" #2752
Adding contextual link back to our Django Server Side Events issue: #2739
As of this comment, we have a release announcement for htmx 2.0.0, initially known as the next
variant as latest
is to remain reference for compatibility purposes to the original 1 series untill Jan 1, 2025.
https://htmx.org/posts/2024-06-17-htmx-2-0-0-is-released/
We should skate to where the puck will be on this front: given we are starting out fresh with htmx in our pending testing phase (hopefully).
https://django-htmx.readthedocs.io/en/latest/installation.html
https://unpkg.com/browse/htmx.org@2.0.0/ https://unpkg.com/browse/htmx.org@2.0.0/dist/
partner rockstor-jslibs issue: https://github.com/rockstor/rockstor-jslibs/issues/38
HTMX looks to be the right way to go on this front, especially given:
See/hear: https://talkpython.fm/episodes/show/437/htmx-for-django-developers-and-all-of-us
There is also Django middleware and PyCharm plugins. PyPi: https://pypi.org/project/django-htmx/ Project Changelog: https://django-htmx.readthedocs.io/en/latest/changelog.html
The aim here would be to swap out the entirety of our rockstor-jslibs for whatever is required to do the same but via HTMX. And in the process eradicate our hands-on JS need entirely; hopefully.
This would be a piecemeal approach where we do one page/section at a time type as we gain familiarity, so likely an initial enlargement of our dependencies: but ultimately the proposed aim here is to standardise on HTMX entirely.
Required Dependencies