ryannhg/elm-spa
1
1
Fork 0
mirror of https://github.com/ryannhg/elm-spa.git synced 2024-11-22 09:44:55 +03:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #46 from Arkham/fix-typo

Browse Source 
Fix small typo in routing guide
This commit is contained in:
Ryan Haskell-Glatz 2020-07-14 18:02:27 -05:00 committed by GitHub
commit aa02e7abe1
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
examples/elm-spa-dev/public/content/guide/routing.md
View File

@ -53,7 +53,7 @@ __Supported Parameters__: Only `String` and `Int` dynamic parameters are support
You can also nest your dynamic routes. Here's an example:
__`Users/User_String/Posts/Post_Id.elm`__
__`Users/User_String/Posts/Post_Int.elm`__
URL | Params
:-- | :--
@ -75,7 +75,7 @@ type alias Url params =
#### params
Each dynamic page has it's own params, pulled from the URL. There are examples in the "Params" column above.
Each dynamic page has its own params, pulled from the URL. There are examples in the "Params" column above.
```elm
type alias Params =

10
examples/elm-spa-dev/public/content/guide/shared.md
View File

@ -1,10 +1,10 @@
# Shared
Whether your sharing layouts or information between pages, the `Shared` module is the place to be!
Whether you're sharing layouts or information between pages, the `Shared` module is the place to be!
## Flags
If you have initial data you hope to pass into your Elm application, you should provide it via `Flags`,
If you have initial data you want to pass into your Elm application, you should provide it via `Flags`.
When you create a project with `elm-spa init`, a file will be created at `public/main.js`:
@ -53,8 +53,8 @@ decoder =
init : Flags -> Url -> Key -> ( Model, Cmd Msg )
init flags url key =
case Json.decodeValue decoder flags of
Ok initialData -> -- Initialize app
Err reason -> -- Handle failure
Ok initialData -> -- Initialize app
Err reason -> -- Handle failure
```
This way, you can create a decoder to gracefully handle the JSON being sent into your Elm application.
@ -106,7 +106,7 @@ This is just an example of using `update` with the `user` field we added earlier
## view
The `Shared.view` function is a great place to render things that should persist across page transitions. It comes with more than just a `Model`, so you can insert the `page` whereever you'd like:
The `Shared.view` function is a great place to render things that should persist across page transitions. It comes with more than just a `Model`, so you can insert the `page` wherever you'd like:
```elm
import Components.Navbar as Navbar