If special characters like ! are used in the title of a form or the label of a question slugify does not remove them which results in an invalid slug

The textarea field should have configurable rows and cols

The form editor should always show a list of questions assigned to that form

See projectcaluma/caluma#212 for how it is implemented in Backend.

In API following types have been renamed:
RadioQuestion -> ChoiceQuestion
CheckboxQuestion -> MultipleChoiceQuestion

See projectcaluma/caluma#265 for more details also on the reasoning.

Naming of radio and checkbox in the frontend can remain as it is a layout decision the user has to be aware of

404 errors must be handled

We should add proper documentation and a demo with ember-cli-addon-docs

Validations should be translated.

A question has the properties isRequired and isHidden. Those should be editable aswell:

Both of the fields are JEXL expressions!

• isRequired: Should only be true or false for now
• isHidden: For this we need to implement a simple JEXL expression editor - this is used to determine whether a question is hidden. The JEXL expression can use the values of other questions (with a transform)

The user should be able to archive forms instead of deleting them. They should not appear in the list of forms (#2) per default but can be accessed by a special filter. Archived forms can not be edited anymore.

The mask from #3 should be used for the creation of a form aswell. However, the slug must be editable and should be a suggestion (slugified name of the form) per default.

Archive and Publish used to be mutations. This has been removed and such are set as flags on save form and save question mutations.

Form Builder needs to be adjusted that such a flag can be set

The list of questions should be sortable per drag and drop

In required questions should be highlighted in the list of questions

Currently we have one acceptance test file for every case. To increase the file count we should have a question test and a form test.

https://github.com/bgentry/ember-apollo-client should actually support this. However, this didn't work out of the box. Maybe we need to configure something to make it work with and addon or engine

See projectcaluma/caluma#255 for backend implementation.

A few things to note:

• A copy of a form will reference the same questions as previous forms
• Copy of questions will reference the same options as previous questions.

Both of this is important that jexl expression are still valid in a new form context.

After a copy has been made user interface has to guide user so it notices when a question resp. option is updated on all form copies or whether the question is only added to current form.

This is especially true for options as user interface looks at them as not global but in the backend they are because of keeping jexl expression valid and multi language support.

At the moment, it could be possible that when creating a form / question the suggested slug is already taken. This should be checked beforehand..

The general information (name and description) should be editable. The mask should appear if the user clicks on a row in the list of forms. Also it should contain a delete functionality

A question must be able to be removed from a form

The user should be able to create a new question

The slug for a new question should be suggested like it is for forms

on-change => onChange

The user should be able to add an existing question to the form. The question must be searchable.

Checkbox and radio questions should have configurable multilingual options

The entrypoint of the form builder should be a list of all created forms. The list should display only the name of the form per default.

Maybe we should add a hint field for questions. Maybe markdown?

We need to improve the navigation flow. The current system with "Back" does not work. Maybe a breadcrumb navigation would be the solution?