The fi.hg.ui from heusalagroup

When the list contains object values, flatten them, eg. {"user":{"name"}} will turn into "user.name" column
Calculate how many rows can be visible in the view for single page
Next and back buttons for page changes
Page number change field
Optional actions menu for items

Optimize builder view on small screens

Current builder view is on two columns horizontally.

This is fine for wider screens, but not so nice for smaller.

So maybe make it flexible so that small screens will change to vertical style.

Support for read only fields

These fields could not be changed but would show the value.

Useful to create views which just show the data.

Pipeline task which sends form values to remote server as a file

Field validations

Add generic support to validate fields and disable the submit if some of the values are not correct.

Support for non-string values in Select builder

Current implementation only accepts string values.

Would be better if any field component could be used as an item value.

Support to configure theme and/or styles for elements

Record component

This component would display an object value in a record style table, eg. it's properties as a key - value table.

The object would be flattened first. Eg, if there's other objects, those would be converted as "person.username", etc.

Useful to display data.

Icon support

Support to add icons on components.

This would require also an Icon registry including a backend implementation.

Consider integrating directly to Noun Project's API so that the end-user can use any icon.

Submit action to post data to REST API

Support to post form data using HTTP request.

Support to define form submit targets in the form

The saved form model needs support to define multiple targets for form submit:

Iframe (default) #17

The rest of will be implemented using the user configurable pipeline implementation (See #70):

Organize previews inside tabs

See #25 for the Tab component.

Currently Preview, Form model and Form value blocks are on the main screen. These could be changed inside tabs.

Calendar component / Date time field

For this, we probably want to use 3rd party component.

Tab component

Simple tab component which can implement blocks of code inside tabs.

Tab builder support

The tab component was created in issue #25 -- but without support to use it in Builder.

It's basically like Select component, except it is tab. It uses the same values model already.

Add placeholder support in the Select field

CSV export saved form data

Action to set form spec and/or initial data from the parent of the iframe

Set initial form model
Set initial form value

Add titles / area labels for buttons which only have the icon

Add support to create form structure from JSON Schema

Like for JSON data in issue #11, this would be nice feature.

Add support to create field structure from JSON document

It would be nice to just submit an JSON document and the form structure would be generated from it.

Email field

Form header area feature

Add support to add a form header area which will be on every page of the form.

Items placed here would be on every page of the form.

This would also allow removing the Main title and placing it as an header element (see #13).

Password field

Fix width of Select builder's items on wider screens

The width was limited to specific length to fix problems on small screens. However, now it's broken on wider screens.

When key is changed on the Builder, change the model value also

This isn't strictly required, since the form's specification shouldn't change in the production, and for sure it should not change the value in there either.

However, when editing the form, it may be user friendly to change the model.