Skip to content

form and response template #182

@kapouer

Description

@kapouer

Currently there are two ways to do something depending on a form response status code (and possibly content too):

  • show a static message (by preparing static messages for each status code or ranges of codes)
  • do a redirection depending on some ranges of status codes, the query parameters of which can depend on current query and form response.

... and this is complicated.
There is also no way to merge response data directly in a template - and this is a huge problem for reporting the result of the api call.
The right way to do it would be:

  • a form is always a template
  • response is always merged
  • to make redirections, just use a "redirector" element (?) or keep current form attributes, as they might allow "batch api calls" - ie chain calls on server.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions