Skip to content
This repository has been archived by the owner on May 7, 2022. It is now read-only.

Decouple validation and form rendering #80

Open
icook opened this issue Sep 7, 2013 · 2 comments
Open

Decouple validation and form rendering #80

icook opened this issue Sep 7, 2013 · 2 comments
Assignees
Milestone

Comments

@icook
Copy link
Owner

icook commented Sep 7, 2013

Allow the validation to be used by multiple data sources more easily. Explore JSONSchema.

@prologic
Copy link

prologic commented Sep 8, 2013

Cool :) So my thoughts (to clarify) are:

Server -> Client

  1. Write form schema(s) using JSON Schema
    2) Translate JSON Schema(s) to Yota form(s)
    3) Render Yota form(s)

Client -> Server

  1. Post form data
  2. Process form data
  3. Apply to JSON Schema(s)

This way we decouple the form validation from the rendering
and make for hooking up storage backends more convenient
since the data is no longer tired to the forms.

@prologic
Copy link

See comment: #75 (comment)

I think this should be merged with Issue #75

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants