This episode explores what an optimistic ui might look like in htmx. Also: is it what we want to do? Is it even possible? Or is it incompatible with the idea of having the dom as the true application state?Original tweet:https://x.com/noahflk/status/1795758603577545035DHH responses: https://x.com/dhh/status/1796163806650868149Htmx guy responses:https://x.com/htmx_org/status/1796182554883539236

{ "HX-Retarget": "#my-special-target" }

Override your "hx-swap=" attribute. Correct your hx-swap mistake! Do it now!!!

{ "HX-Refresh": "true" }

Decide from your server side what url the user sees!https://htmx.org/headers/hx-push-url

Speaking with a prolific developer who recently switched from React to htmx

Redirect your users to a new page from your back-end server in SPA-mode (no refresh for them)https://htmx.org/headers/hx-location/

This header is to make sure your system loads the full page when 1) You are suing hx-push-url to work with the url bar2) Users click the back button.3) The full page cached history snapshot isn't thereUseful links mentioned:https://github.com/bigskysoftware/htmx/issues/497https://htmx.org/docs/#history

The htmx request header that tells youEXACTLY where the user is making the request fromThe full url string with all ids and params

A case for taking the extra steps. It's a good thing