Decode json into elm using schema

Question

Decode json into elm using schema

1602 opened this issue 8 years ago · 3 comments

It might be useful to use json schema in place of traditional decoders in some cases. This is research and not development.

Answer 1 · 2017-11-07T13:36:19.000Z

Conclusion?

Answer 2 · 2017-11-07T14:30:36.000Z

@jpierson the conclusion: JSON Schema doesn't have a sufficient amount of information to be decoded into elm values. It will work in limited cases for example if you have flat object which consists of strings, numbers, booleans, or list of primitives. Union types, tuples and more fluffy structures is a big obstacle here. Dealing with those would mean having additional abstraction level on top of JSON Schema, so traditional decoders would be a nicer solution in this case (less complexity involved).

It might worth reopening this later though, if there will be more interest in the future. Speaking frankly I just struggle to find a good enough use-case for this, hence it doesn't worth any more time invested in this research.

Answer 3 · 2017-11-09T05:09:22.000Z

This makes sense. Thank you for the thoughtful explanation.

…

On Tue, Nov 7, 2017, 9:30 AM Anatoliy ***@***.***> wrote: @jpierson <https://github.com/jpierson> the conclusion: JSON Schema doesn't have a sufficient amount of information to be decoded into elm values. It will work in limited cases for example if you have flat object which consists of strings, numbers, booleans, or list of primitives. Union types, tuples and more fluffy structures is a big obstacle here. Dealing with those would mean having additional abstraction level on top of JSON Schema, so traditional decoders would be a nicer solution in this case (less complexity involved). It might worth reopening this later though, if there will be more interest in the future. Speaking frankly I just struggle to find a good enough use-case for this, hence it doesn't worth any more time invested in this research. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <https://github.com/1602/json-schema/issues/22#issuecomment-342499265>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABZjCgWd8Bv_vc0etZ7tNkF3j_MY_T_tks5s0GmMgaJpZM4O-UBi> .