From 1d8d13d766b6467188cbded28d103ffb13421c77 Mon Sep 17 00:00:00 2001 From: Eileen Noonan Date: Fri, 22 Mar 2024 15:26:14 -0400 Subject: =?UTF-8?q?=F0=9F=94=80=20Write=20a=20readme=20for=20example=2004-?= =?UTF-8?q?custom-event-handlers.=20(#72)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * readme for example 04 * Update README.md tweaks --- examples/03-controlled-inputs/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'examples/03-controlled-inputs') diff --git a/examples/03-controlled-inputs/README.md b/examples/03-controlled-inputs/README.md index 4696c6d..fcbbb1f 100644 --- a/examples/03-controlled-inputs/README.md +++ b/examples/03-controlled-inputs/README.md @@ -31,7 +31,7 @@ ui.input([ Central to Lustre's architecture is the idea that your model is the single source of truth for your application's UI. This opens up the door to things like serialising -progam state to load in the future, time-travel debugging, and rehydrating your +program state to load in the future, time-travel debugging, and rehydrating your app's state from a server. It also gives you tighter control of when and how to update your UI in response -- cgit v1.2.3