Command Registry

Associates listener functions with commands in a context-sensitive way using DOM node. You can access a global instance of this class via inkdrop.commands.

The global command registry facilitates a style of event handling known as event delegation. Inkdrop commands are expressed as custom DOM events that can be invoked on the currently focused element via a key binding. Rather than binding listeners for command events directly to DOM nodes, you instead register command event listeners globally on inkdrop.commands and constrain them to specific kinds of elements with DOM nodes.

Command names must follow the namespace:action pattern, where namespace will typically be the name of your package, and action describes the behavior of your command. If either part consists of multiple words, these must be separated by hyphens. E.g. awesome-package:turn-it-up-to-eleven. All words should be lowercased.

As the event bubbles upward through the DOM, all registered event listeners with matching selectors are invoked in order of specificity. In the event of a specificity tie, the most recently registered listener is invoked first. This mirrors the "cascade" semantics of CSS. Event listeners are invoked in the context of the current DOM node, meaning this always points at event.currentTarget. As is normally the case with DOM events, stopPropagation and stopImmediatePropagation can be used to terminate the bubbling process and prevent invocation of additional listeners.


add(target, commandName, callback)

Register a command

Add a command listener associated with a DOM node.

Parameters

  • Name
    target
    Type
    DOM node
    Required
    Description

    A DOM node.

  • Name
    commandName
    Type
    string
    Required
    Description

    A string indicating the command's name, e.g., user:insert-date.

  • Name
    callback(event)
    Type
    function
    Required
    Description

    A function called when the command is invoked on an element matching the selector. It references the matching DOM node.

Here is a command that inserts the current date in an editor:

Example

inkdrop.commands.add(
  document.body,
  'custom:insert-date',
  (event) => {
    const { editingNote } = inkdrop.store.getState()
    const body = editingNote.body + '\n' + new Date().toLocaleString()
    inkdrop.store.dispatch(actions.editingNote.update({ body }))
    inkdrop.store.dispatch(actions.editor.change(true))
  }
)

add(target, commands)

Add multiple commands

Add multiple command listeners associated with a DOM node.

Parameters

  • Name
    target
    Type
    DOM node
    Required
    Description

    A DOM node.

  • Name
    commands
    Type
    object
    Required
    Description

    An object mapping command names like user:insert-date to listener functions.

Example

inkdrop.commands.add(document.body, {
  'custom:insert-date': () => {
    const { editingNote } = inkdrop.store.getState()
    const body = editingNote.body + '\n' + new Date().toLocaleString()
    inkdrop.store.dispatch(actions.editingNote.update({ body }))
    inkdrop.store.dispatch(actions.editor.change(true))
  }
})

dispatch(target, commandName, detail)

Dispatch the given command

Simulate the dispatch of a command on a DOM node.

This is useful for testing, especially when simulating a command's invocation on a detached DOM node. Otherwise, the DOM node must be attached to the document so the event can bubble up to the root node.

Parameters

  • Name
    target
    Type
    DOM node
    Required
    Description

    The DOM node to start the command event bubbling.

  • Name
    commandName
    Type
    string
    Required
    Description

    A string indicating the command's name.

  • Name
    detail
    Type
    object
    Description

    Parameters to be passed.

Example

inkdrop.commands.dispatch(document.body, 'core:save-note')
Can you help us improve the docs? 🙏

The source of these docs is here on GitHub. If you see a way these docs can be improved, please fork us!