mirror of
https://github.com/bigskysoftware/hypermedia-systems.git
synced 2025-08-10 00:04:18 -04:00
Compare commits
No commits in common. "fb0408b75107ad4699c45055ed9002d8a91755e5" and "74f25213c0f104d75c08410a4b839c792160bf19" have entirely different histories.
fb0408b751
...
74f25213c0
@ -336,7 +336,7 @@ In the interest of keeping our application simple, we are going to omit that mor
|
||||
|
||||
We have updated the client-side code (if HTML can be considered code) so it now issues a `DELETE` request to the appropriate
|
||||
URL, but we still have some work to do. Since we updated both the route and the HTTP method we are using, we are going to
|
||||
need to update the server-side implementation as well to handle this new HTTP request.
|
||||
need to update the server-side implementation as well to handle this new HTTP Request.
|
||||
|
||||
.The original server-side code for deleting a contact
|
||||
[source, python]
|
||||
|
@ -276,7 +276,6 @@ both buttons in a `div` and eliminate the redundant `hx-target` specification by
|
||||
Here is our updated code:
|
||||
|
||||
(((hx-sync, example)))
|
||||
|
||||
.Syncing two buttons
|
||||
[source, html]
|
||||
----
|
||||
|
@ -128,7 +128,6 @@ Note that by splitting these two APIs apart, you reduce the pressure to constant
|
||||
This is the key advantage of splitting your Data API from your Hypermedia API.
|
||||
|
||||
((("REST API")))
|
||||
|
||||
.JSON Data APIs vs JSON "`REST`" APIs
|
||||
****
|
||||
Unfortunately, today, for historical reasons, what we are calling JSON Data APIs are often referred to as
|
||||
|
Loading…
x
Reference in New Issue
Block a user