From 1fe11c9253a0077cce3a73a2ee96dcc7e158f6c7 Mon Sep 17 00:00:00 2001 From: Dillon Kearns Date: Wed, 24 May 2023 14:39:47 -0700 Subject: [PATCH] Remove fetcher module which is now covered inline in package docs. --- examples/docs/content/docs/10-fetchers.md | 17 ----------------- 1 file changed, 17 deletions(-) delete mode 100644 examples/docs/content/docs/10-fetchers.md diff --git a/examples/docs/content/docs/10-fetchers.md b/examples/docs/content/docs/10-fetchers.md deleted file mode 100644 index 62bbfbc1..00000000 --- a/examples/docs/content/docs/10-fetchers.md +++ /dev/null @@ -1,17 +0,0 @@ -# Fetchers - -The difference between a Fetcher and the built-in submission/page reloading Effects/Msg's is: - -## Fetcher - -- Doesn't cause a page change ever -- Gives you a Msg back when the data arrives -- Can have multiple concurrent fetchers - -## Non-Fetcher - -- Available through static argument in view/init/update (not a Msg), so you don't need to keep anything in your Model (the static.data : Data and static.action : Maybe ActionData) -- Only one in-flight at once -- Can cause a page navigation - -So if you don't want to keep things in your Model at all, you just don't use fetchers, and you can have a dynamic app with client-side submissions where the client-side state is entirely owned by elm-pages by accessible to the user