User Actions

The user actions UI for Mono.

How to use

Include the module in the application descriptor.

"MIID_NAME": {
    "module": "github/jxmono/user-actions/MODULE_VERSION",
    "roles": MONO_ROLES,
    "config": {
        "html": PATH_TO_HTML_FILE
        "waitFor": WAIT_FOR_CONFIGURATION
    }
}

The html file that is loaded by this miid must have elements with known selectors. Example:

<span class="myClass">
    <button data-action="action-1">Action 1</button>
    <button data-action="action-2">Action 2</button>
    <button data-action="action-3">Action 3</button>
    <button data-action="action-4">Action 4</button>
    ...
    <button data-action="action-n">Action n</button>
</span>

In the CRUD role object you will define the actions:

role_name: {
    _id: ids.roles.role_name,
    _tp: [ids.templates.d_roles],
    name: 'Role Name',
    actions: [
        {
            template: 'TEMPLATE_ID',
            selector: '[data-action="action-1"],[data-action="action-2"]',
            filter:   {
                'some': 'query'
            }
        },
    ]
},

Changelog

v0.3.0

• transferred the module to the new jxMono organization
• updated Bind to v0.4.0, Events to v0.4.0

v0.2.1

• Updated to Bind v0.3.1

v0.2.0

• Handle filters that are strings (emit server events)
• Simplified the code from the CRUD response callback
• Updated deps

v0.1.2

• Fixed hanging request when no actions were found for a specific template, role, and item. The server returns an empty object if no actions were found.
• Added configurable action selector for hiding before rendering new correct actions with default value [data-action]:

"config": {
    "ui": {
        "selectors": {
            "action": "[data-action]"
        }
    }
}

v0.1.1

• Default value for actions

v0.1.0

• Initial stable release