In case of unsaved data in single object view page an alert must appear to user

• automagically generate build files for distribution from sources
• publish builds (CDN or different repo…)
  • remove development builds from repo and ignore

show correct folder tree

Response data in meta.thumbnails could contain info acceptable and ready.
Thumb helper should manage these cases:

• acceptable is false, thumbnail for image won't be created
• acceptable is true (or is absent) and ready is false, thumbnail for image is still not available, but it will
• acceptable is true (or is absent) and ready is true, thumbnail is available

Trying to save extra field doesn't work. The field is left at NULL value.

In single object view:

• display all available relations
• for each relation a paginated list of related objects should be displayed with params - use ajax (??)
• add object to relation -> modal view?
• remove related object
• modify related object params or relation position

Instead of associating existing objects we may need to create and associate new objects.
Typical use case: new files or images to attach -> upload action necessary.

see bedita/php-sdk#3

After bedita/bedita#1515 we must properly handle the new date type.

PS: currently in Profiles saving a birthdate generates an error

In related objects panel using add objects we need:

• query filter to perform simple search using q query string
• pagination
• type selection if more types are available (this can be done later in another issue)

Date attributes with JSON Schema type:

{
  "type": "string",
  "format": "date-time"
}

should have a datepicker UI widget

Every folder object can belong to only one folder or be root folder.
Select parent root browsing the tree.

After #37 object view refactor a new relations layout is needed

Refactor is necessary

Success message should automatically disappear after a few seconds - or user must not be forced to click.
On error message a user may instead be forced to click, but other options are possibile.

In /model/relations/$id inside data.attributes.params we may have a JSON Schema representation of the relation properties, could also be empty.

In the object card now relation parameters are displayed but may not be changed.
Form handling with JSON Schema should keep advantage of existing SchemaHelper

In media and images index display a thumbnail if available

Page with logged user data from User: ### on left menu

User should be able to change properties like:

• password - with password confirm
• name, surname, email.... and other attributes like city, address if available

Unchangeable properties:

• username
• uname
• status

Current roles can be displayed but not changed

single object view should display included stream, if present
call to GET /images/{id} may include also:

 "included": [
        {
            "id": "b1f3e797-558d-4310-a9dc-f0c19927eb85",
            "type": "streams",
            "attributes": {
                "file_name": "my-image.png",
                "mime_type": "image/png"
            },
            "meta": {
                "version": 1,
                "file_size": 122927,
                "hash_md5": "23de017e93556d45f5b69dd508a868f7",
                "hash_sha1": "74fa37b617a0daad926c68d66fc451a246943ae5",
                "width": null,
                "height": null,
                "duration": null,
                "created": "2018-03-14T08:25:54+00:00",
                "modified": "2018-03-14T08:25:54+00:00",
                "url": "http://example.com/files/b1f3e797-558d-4310-a9dc-f0c19927eb85-doorway-platform.png"
            }
        }
    ]

attributes and meta shoud be displayed read-only they're not chengeable
link to image and image itself should be displayed.
[https://github.com/bedita/php-sdk/issues/10 will provide thumb generation, soon]

• property-view component handles keyboard instead of jquery
• css transition instead of jquery ui

API errors are handled but Internal app errors view are still missing.

Example: /documents/view or /documents/abc return missing controller page

• only available to admin users
• basic handling of relations, object_types, properties and property_types

see https://docs.bedita.net/en/latest/endpoints/model/index.html

add password input field with minimum validation

• only available to admin users
• basic handling of applications, jobs, config and custom endpoints
• also roles ??

checkout:

• gulp;
• webpack 4;
• parceljs;

goals:

• simple conf;

After bedita/bedita#1501 password change is allowed if the current valid password is also provided

Instead username and email should be readonly for now-

After #112, relation panel contains filter search and pagination links.
Still to do:

• better styles for pagination links (i.e. 1 ... [n-1] [n] [n+1] ... m)
• show loader
• show total items by filter/search

Field order and positioning refactor.
Two columns and different attributes groups.

add vue to object view page

Like in BE3 a simple input to load directly an object by its id or uname

Form fields order in user view (existing o new) is misleading.

Main attributes here are:

• username and passowrd - confirm password fields
• name
• surname
• email

All other attributes may go in other attributes

Used in media object types view:

• if object is remote with embedded HTML player -> display the player
• if an image with a stream create a thumbnail with ThumbHelper

Current groups:

• index - list view
• core - core module properties
• other - simply defined as all properties - core

Define new groups with configuration and set new groups for views

Implement first filter: text search - other filters will come later

• https://docs.bedita.net/en/latest/endpoints/parameters.html#search-query-filter - use filter[query] or q query string
• buttons: 'find(orapply) and reset filter`
• filter must persist with pagination

Better UI/UIX for import page with filters.

add datepicker for date fields in views

Basic import page using filters.
Source should be a list of available filters (type / options).
On submit file, system should read file, process it and return a result.

In single object view:

• display all available relations
• for each relation a paginated list of related objects should be displayed with params - use ajax (??)
• add object to relation -> modal view?
• remove related object
• modify related object params or relation position

in related objects priority number must be displayed and user should be able to change priority order
Only in relation parameters view (for now)
After #133

Desiderata:

• Mantain filter after click on Restore and Delete
• Empty trash button (when filter selected, remove only current type, i.e. media, when page is /trash?filter%5Btype%5D=media, otherwise remove all objects from trash)

Uniform error layout and pages to default layout with minimalist style.

when a relation has multiple types a type filter should be available in both new objects assignment and in already related objects block.

Colors cannot be statically defined in CSS like in BE3

Initial proposal:

• in config/app.php

    'Modules' => [
        'colors' => [
            'documents' => '#FF6600',
            'users' => '#555555',
            'profiles' => '#003366',
       ],
   ],

• simple inline CSS in default layout inside <head> tag using element

In module index page, it should possible perform bulk operations on elements, i.e.:

• move to trash
• change status (on/off/draft)
• csv export (selected|all) ?

When number of related objects is high we need to activate search query on already related objects.
Same search is used when looking for new objects to associate.

Attributes with JSON Schema type:

{
  "type": "string",
  "contentMediaType": "text/html"
}

Should be displayed using a richtext editor like CKEditor

A JSON schema like the one provided below must be handled with checkboxes or other control in object view form.

{
  "type": "array",
  "uniqueItems": true,
  "items": {
      "type": "string",
      "enum": ["A", "B", "C", "D"]
  }
}

We don't need a general purpose array handler for now.
A simple string list case, like the one above, is enough.

parents relation for every object not of type folders should display a browsable tree of available foders to select like in BE3

The SchemaHelper for checkbox doesn't generate checkbox in the right way.

For example see company field in Users object type. The checkbox is always checked and changing the check doesn't reflect on save.

When in module list, selecting and deselecting multiple times brings to inconsistencies in the hidden input containing the array of ids.