Re:The Hypermedia-Driven Application (HDA) Architecture
by murkt on Sunday February 06, 2022 @03:16PM
(#30236553)
Just generate these ids on the server. For example, when I render a new field for which I need a delete button, I send numbers of other fields along with them, and server renders a new field for me with a new id.
[ Parent
| on HN ]
Re:The Hypermedia-Driven Application (HDA) Architecture
by nvegater on Sunday February 06, 2022 @03:25PM
(#30236636)
Thanks for responding. If I understand correctly, then I would need a server like nodejs or django generating and sending the "index.htmx" to the browser and then responding to users interactions by embedding the data from the server inside of the htmx files, correct?
Re:The Hypermedia-Driven Application (HDA) Architecture
by murkt on Sunday February 06, 2022 @03:30PM
(#30236666)
Sounds about right.
It’s the good old server templates (we use Jinja), and for interactivity I have additional attributes here and there, and sometimes additional endpoints.
It’s miles better than full-fledged JS SPA. I’ve had React+GraphQL app that I’m migrating piece by piece when we need a new feature, and it’s a few times faster to do and easier to understand.