Skip to content

Implement a "Form" flow node type #13

@GabrielMajeri

Description

@GabrielMajeri

The "Form" node type is used to generate custom form pages.

Properties

  • Slug: symbolic name of the form (e.g. adeverinte-studenti), will become a component of the final URL (e.g. localhost:3000/public/<organization name>/<form slug>);
  • Title: heading displayed in the rendered form (string, limited to 32 characters);
  • Description: body of text displayed under the form's header. Can contain Markdown (but not raw HTML!) and will be rendered upon the page's generation.
  • Fields: a list of form fields, of various types (text fields, check boxes, radio buttons, dropdowns, file uploads etc.)
    • Each field contains, at the least, the following properties:
      • id: slug-like identifier, which will be used when saving the form response in the DB (corresponds to the HTML input's name field). This ID must be unique per-form (two fields cannot have the same ID).
      • type: type of the field (whether it's a text field, a check box, a dropdown etc.)
      • label: text label displayed when the field is rendered; tells the users what they must fill in here.
      • required: boolean indicating whether this field must be filled in before a form can be submitted, or not.
    • Text fields and check boxes don't have any additional data.
    • Radio button fields and dropdowns have an additional property called options, which is a comma-separated list of possible values.

Metadata

Metadata

Assignees

No one assigned

    Labels

    front-endIssues related to the app's front end

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions