Code review comment for lp:~cprov/uci-engine/webui-create-ticket

On Tue, Sep 23, 2014 at 03:30:48PM -0000, Celso Providelo wrote:
> Joe,
>
> I've experimented with this idea and realize that the form generation
> is not part of the API provider, it already offer us REST primitives
> and it is good at it.
>
> The forms are related to the way the UI is layed and users want to use
> it, a single form will probably involve data from many models and will
> be executed via multiple REST posts.
>
> Long story short, building forms on TS would be going in the wrong
> direction by artificially coupling UI to Models (not APIs), to not
> mention the additional django view + forms which would tie us even
> more to django for a simple REST wsgi app.
>
> The way it's is done, the form is built and validated client-side in
> terms of the information users want to provide and submitted according
> to what our API allows us to do.
>
> Do you see it differently ?

If having the TS generate the forms is not optimal then I'm fine with
that. Are we able to utilize the API schema on the client-side so that
the TS can communicate its data requirements?