there is some sort of rendering bug in Firefox (tested with 59.0.3)

domain edit is cut off initially, if you open firebug it's gone

js is included twice, if there are more than one instance of a custom form type. Therefore vue CustomElementRegistry tries to register the same name twice.

• Make DomainMember entity fieldable
• Allow to define member types per domain

Instead of firstname / lastname we should only have one name field. The name field should identify the user and could also be a company name, so we should not force to enter a firstname and a lastname

• Title should include member type name
• Improve invitation table display
• Update title should be something like "Update Users membership for Franz Wilding"
• Delete title should be something like "Delete Users membership for Franz Wilding"
• Table should include a dedicated column for accessor type (user or api key), this should be an icon with hover title
• Refactor domain invite process: First step: "select existing user / Select API key / invite user", next step: "select role"

On many places (for example the headline on content update page), a content entity must be named. In order to do this, the Content class should implement __toString().

__toString() should use an content_label property on the ContentType entity to figure out, which fields to display as title. This property can also become the default for reference field to avoid double definition of content_label

content_label should default to "{type} #{id}" or something reasonable.

To allow cross-domain references, api clients must have access rights to multiple domains. At the moment this is not possible, because they are managed per domain.

Proposed solution: Manage api clients per organization and allow to set the domains, they have access to.

At the moment there are Users and ApiClients that are managed per organization (after implementing #20). They only have an identifier and roles.

In the future we probably need a way other individuals can authenticate against the api (via oauth) and also fields on each of this user entities.

Implement graphQL mutations to delete, restore and delete-definitely content. This is already implemented in ContentController and can easily be re-implemented as graphql mutation types.

Consider to refactor the actions by creating some service that takes care of content deletion and will be used in the controller and the mutation.

• ORG API Key tokens should be hidden by default and only displayed on click
• ORG API Key Delete screen should look more like content delete screen
• ORG User Table should follow table styles
• ORG User Table Domains should display domain member type nicely
• ORG User Table ROLES should only be flag "ADMINISTRATOR / USER"
• ORG User Form ROLES should only be checkbox: "ADMINISTRATOR"?
• ORG User Delete screen should look more like content delete screen

Idea: https://symfony.com/doc/4.0/components/expression_language.html

todos:

• Save Graphql field query to preview to know what we need to send to the preview endpoint
• Finish ContentController:preview action (use real content type and field query)
• Implement SettingController:preview action
• Check on change events for custom form elements (collection, file, wywiwyg)

We switch from uikit icons to the https://feathericons.com/ iconset. Icons that are used for the UI as well as icons, that can be selected for contenttypes and settingtypes must change to the new icon set

Replace the reserved word "collections" with "views" and write / update an unit test to check this

For a nicer media handling implement a view for displaying files and images. The view should look something like dropbox or google drive and should include a drag-and-drop upload area.

The view should also implement selection from reference field

Removing setting types from the domain configuration has no effect

Implement all left field types, which are easy to implement

See symfony form types
https://symfony.com/doc/current/reference/forms/types.html

• Allow Users to create new organizations
• Maybe we need a config to disable this feature for custom installations, where one administrator is responsible for managing organizations?
• They will be ORG_ADMIN for the new organization
• We need a route where user can see all their organizations

Create a new design and refactor the base user interface

Rename all "United" with classes, services and directories with "Unite".

All users must be allowed to cancel their accounts. Also when not using the registration bundle, users can be invited to the platform and therefore should be able to cancel their account again.

• platform admins can be deleted at any time
• org_users can be deleted at any time
• When deleting org_admins, there must be at least on admin left for each org

For defining dynamic field input, a https://www.drupal.org/project/paragraphs - like field type should be implemented. It allows to define types with a fields set each. The user can choose one type and fill out the fields of this type.

todos

• From javascript (vue component). Maybe we can use this also for domain member add form.
• GraphQL input and output types
• Remove unused variants before save to database
• Form rendering tests
• Nested event delegation. Almost done but need a little change when #207 is implemented
• Test graphql filter and sort selectors
• Test Storage and Sortable view combination

We need two more configuration options for the storage bundle to allow to select the s3 region and a subfolder path, where the files will be stored.

• Remove DomainMember Roles
• Remove Domain allowed Roles
• Check access via an expression language statement https://symfony.com/doc/current/components/expression_language.html

Api routes should be changed because it will be difficult to match all these routes in the future

current regex ApiRequestMatcher
^/[A-Za-z0-9_-]+/[A-Za-z0-9_-]+/api(/|$)

fe.
/test/first/api
/test/first/api/content/news/upload (doesnt match ^/[A-Za-z0-9_-]+/[A-Za-z0-9_-]+/api(/.+|$) is no good approach)

should be changed to

/api/test/first
/api/test/first/content/news/upload

Config is a mess. Clean it up, split it into multiple files and add comments

write a test case for CollectionFieldType which does a POST request through main firewall with crsf protection

https://github.com/vuejs/vue-web-component-wrapper

preferably based on vue.js

some Files have 2 space intention instead of 4

Task:
Finde those Files and clean them up!

Translation missing: content.delete_definitely.submit

With domain members and api keys moved to the sidebar menu, the dropdown menu only contains the admin links "update domain" and "delete domain". Move the two buttons below the dropdown menu for a improved UI

• When removing organization admins, make sure that there is at least one organization admin left.
• When deleting user accounts, make sure that for each organization, this user is an admin, there must be another admin left

Implement a graphQL mutation to revert content and setting to a specific version. This is already implemented in ContentController::revisionsRevertAction and SettingController::revisionsRevertAction and can easily be re-implemented as a graphql mutation type

http://symfony.com/doc/current/security/multiple_user_providers.html

CollectionFieldType::onUpdate only calls onUpdate on all child fields. However, for the child a row-add or row-delete action is a create or hard-delete action.