dillonkearns/elm-pages-v3-beta
1
1
Fork 0
mirror of https://github.com/dillonkearns/elm-pages-v3-beta.git synced 2024-12-23 11:55:41 +03:00
Code Issues Packages Projects Releases Wiki Activity

Remove fetcher module which is now covered inline in package docs.

Browse Source
This commit is contained in:
Dillon Kearns 2023-05-24 14:39:47 -07:00
parent c36ab1ccac
commit 1fe11c9253
1 changed files with 0 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
examples/docs/content/docs/10-fetchers.md
View File

@ -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