Skip to content

Fix link to Json Value type in interop guide #477

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 1, 2016
Merged

Fix link to Json Value type in interop guide #477

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/guide/chapters/interop.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -130,6 +130,6 @@ The particular types that can be sent in and out of ports is quite flexible, cov
* **Records** – correspond to JavaScript objects
* **Signals** – correspond to event streams in JS
* **Maybes** – `Nothing` and `Just 42` correspond to `null` and `42` in JS
* **Json** – [`Json.Value`](http://package.elm-lang.org/packages/elm-lang/core/latest/Json) corresponds to arbitrary JSON
* **Json** – [`Json.Encode.Value`](http://package.elm-lang.org/packages/elm-lang/core/latest/Json-Encode#Value) corresponds to arbitrary JSON

All conversions are symmetric and type safe. If someone tries to give a badly typed value to Elm it will throw an error in JS immediately. By having a border check like this, Elm code can continue to guarantee that you will never have type errors at runtime.