Validation for Form Schemas

[quietlyconfident]

Definitions

• Form Schema (AKA "Schema") A JSON document which describes a form (e.g. a Contact Name & Address Form)
• Form Schema Specification (AKA "Spec") - A JSON Schema document which can be used to validate a Form Schema.

Issue

There should be a Spec against which a Schema can be validated. angular-schema-form creates the form from the schema and also validates the form fields against the same schema.

[quietlyconfident]

There is a specification here: https://github.com/formly-js/angular-formly/wiki/JSON-Specification . It just isn't a JSON-Schema specification.

This is hitting below the belt, because the author admitted on posting that it was very beta :) But nonetheless there is a spec.

[quietlyconfident]

Slight clarification here; I was not fully educated in how angular-schema-form worked.

In angular-schema-form:

1. The Form Schema is itself a JSON Schema, and
2. There is not (yet) a Form Schema Specification. In other words, you cannot mechanically validate your Form Schema.

Nonetheless, I think the suggestion / request stands. . . it would be good to have a formal schema specification for against which an individual Form Spec could be validated.

[kentcdodds]

I have no idea what this is all about... What do you want us to do?

[quietlyconfident]

Ha ha, mostly what I want you to do is consider and tell me what you think. This is related to the "integration with a form-builder" discussion.

To integrate with a form builder program, the form-builder will need to create output in a format that the form-displaying program (angular formly) can understand. Often, when this sort of thing is done, the pattern is to develop a contract (e.g. API, schema, etc.) that both applications / layers / etc. can depend on.

I propose that this contract should be a JSON Schema document, because then you could use an out of the box schema validator on either the client side (e.g. tv4) or the server side (e.g. a python / ruby package) to validate the "form" that has been built by the form builder.

[kentcdodds]

I see... Sounds useful. I don't know if I have the time to work on it now
though...

• Kent C. Dodds
  Sent from my mobile device, please forgive any errors or brevity. (I may
  have used speech to text...)
  On Oct 6, 2014 2:36 PM, "Erik Dykema" notifications@github.com wrote:

Ha ha, mostly what I want you to do is consider and tell me what you
think. This is related to the "integration with a form-builder" discussion.

To integrate with a form builder program, the form-builder will need to
create output in a format that the form-displaying program (angular formly)
can understand. Often, when this sort of thing is done, the pattern is to
develop a contract (e.g. API, schema, etc.) that both applications / layers
/ etc. can depend on.

I propose that this contract should be a JSON Schema
http://json-schema.org/ document, because then you could use an out of
the box schema validator on either the client side (e.g. tv4) or the server
side (e.g. a python / ruby package) to validate the "form" that has been
built by the form builder.

—
Reply to this email directly or view it on GitHub
#114 (comment)
.

[kentcdodds]

There's the beginnings of a form schema specification here. It's a little difficult to generalize things because different formly components can require such different things, but I think most of the common stuff is there.