You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My intuition tells me that there should be some way to take a JsonSchema and end up with a decoder that generates a Type derived from the JsonSchema...
Is this the intention of the project or is it planned for doing validations on the api separate from the payload decode?
The text was updated successfully, but these errors were encountered:
You mean take a normal JSON schema and decode it into an elm-schema? Definitely! @norpan laid down the foundation for that in #5. Check #3 for an idea of what this could be used for and #6 for some progress on supporting additional schema's.
Or are you talking about taking a schema and generation a decoder, elm code to decode such a schema? That could be a really interesting application too!
I'm going to use this to make forms from schemas and validate them, using the Value type internally in the forms. I have user specified data (specified by writing JSON schemas) in a RethinkDB database that I want to offer forms to edit.
And yes, that includes forms to edit the JSON schema itself, maybe using the JSON schema schema :)
This is interesting..
My intuition tells me that there should be some way to take a JsonSchema and end up with a decoder that generates a Type derived from the JsonSchema...
Is this the intention of the project or is it planned for doing validations on the api separate from the payload decode?
The text was updated successfully, but these errors were encountered: