mirror of
https://github.com/bigskysoftware/hypermedia-systems.git
synced 2025-12-05 00:03:55 -05:00
minor edits. ds_store...?
This commit is contained in:
parent
fa45af720e
commit
4f53677dde
@ -597,7 +597,7 @@ important to understand the overarching idea of _resources_ and _hypermedia repr
|
||||
getting worked up about the smaller details of your URL design.
|
||||
|
||||
We recommend you just pick a reasonable, resource-oriented URL layout you like and then stay consistent. Remember,
|
||||
in a hypermedia system, you can always change your end-points later, because you are using hypermedia as the engine
|
||||
in a hypermedia system, you can always change your endpoints later, because you are using hypermedia as the engine
|
||||
of application state!
|
||||
****
|
||||
|
||||
|
||||
@ -296,7 +296,7 @@ transferring HTML.
|
||||
|
||||
Thankfully, now, with htmx, we have a chance to rectify this situation.
|
||||
|
||||
The "`right thing`", from a RESTful, resource oriented perspective is, rather than issuing an HTTP `POST` to
|
||||
The "`right thing,`" from a RESTful, resource-oriented perspective is, rather than issuing an HTTP `POST` to
|
||||
`/contacts/42/delete`, to issue an HTTP `DELETE` to `/contacts/42`. We want to delete the contact. The contact is
|
||||
a resource. The URL for that resource is `/contacts/42`. So the ideal is a `DELETE` request to `/contacts/42/`.
|
||||
|
||||
@ -767,8 +767,8 @@ Well, no.
|
||||
|
||||
It turns out that you can implement this functionality in htmx, using pure HTML attributes.
|
||||
|
||||
((hx-trigger, change))
|
||||
((hx-trigger, keyup))
|
||||
(((hx-trigger, change)))
|
||||
(((hx-trigger, keyup)))
|
||||
(((event, change)))
|
||||
(((event, keyup)))
|
||||
In fact, all we need to do is to change our trigger. Currently, we are using the default trigger for inputs, which is the
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user