🐛 Avoid a race condition when dispatch is used twice from outside (#8)

* Upgrade examples to lustre 2.0

* Upgrade to gleam 0.27.0

* Fix: avoid a race condition when dispatch is used twice from outside

E.g. websocket open + websocket msg arriving
Application returns a Cmd from update(model, msg)
but the Effect handler is *not* ran be React 18 before
the websocket msg-arriving is handled by the Reducer.
Result: The Cmd returned by update(model, msg) is dropped silently.

---------

Co-authored-by: Kero van Gelder <kero@chmeee.org>

1 files changed, 1 insertions, 1 deletions

diff --git a/test/example/main.gleam b/test/example/main.gleam
index 7d9c063..21c4067 100644
--- a/test/example/main.gleam
+++ b/test/example/main.gleam
@@ -15,7 +15,7 @@ pub fn main () -> Nil {
     // `lustre.start` can return an `Error` if no DOM element is found that matches
     // the selector. This is a fatal error for our examples, so we panic if that 
     // happens.
-    assert Ok(dispatch) = lustre.start(program, selector)
+    let assert Ok(dispatch) = lustre.start(program, selector)
 
     dispatch(Counter(counter.Incr))
     dispatch(Counter(counter.Incr))