Documentation for JSON.Decode.Value is misleading

[arowM]

In master branch, documentation about JSON.Decode.Value is as follows.

A JSON value.

But I guess it is misleading because Value is now not only for JSON objects.
(Though it is defined in JSON.Decode module...)
For example, it is also used for Html.Events.on to handle Event object, which is not exactly the JSON object.
In another instace, we use Value as an input/output type of ports to handle some JS objects that Elm cannot handle such as File object.
(In fact, I have not realized that Value can be used to pass File object to ports at first.)

P.S.
I'm not sure that this is the right place to report about JSON.Decode module because it seems to be moving to independent package, so if this is not the right place, I'll apologize.

[toraritte]

Value is originally defined in Json.Encode and it is only aliased in Json.Decode. On the other hand, Json.Encode.Value's documentation is more general by saying that it "represents a JavaScript value".

https://github.com/elm-lang/json/blob/master/src/Json/Encode.elm#L35
https://github.com/elm-lang/json/blob/master/src/Json/Decode.elm#L405

[toraritte]

Value is originally defined in Json.Encode and it is only aliased in Json.Decode. On the other hand, Json.Encode.Value's documentation is more general by saying that it "represents a JavaScript value".

https://github.com/elm-lang/json/blob/master/src/Json/Encode.elm#L35
https://github.com/elm-lang/json/blob/master/src/Json/Decode.elm#L405

[arowM]

Thanks. So, how about using the same documentation as Json.Encode.Value to avoid confusion.

[arowM]

Thanks. So, how about using the same documentation as Json.Encode.Value to avoid confusion.

[evancz]

Making the PR about it the canonical one for this

[evancz]

Making the PR about it the canonical one for this