Pro 6843 context menu additional items

[ValJed]

PRO-6843

Summary

I need to add in palette a new item in the context menu.
This item should not open any modal but just emit an event I could listen to know user clicked on it. So I cannot use customOperations here.

I just added the possibility to pass an array of extra items to a AposDocContextMenu component.
This one can be used to call an action like we already do, or to emit a simple event when closing to the parent, like I do with palette.

It allows me to do this in palette:

          <AposDocContextMenu
            :doc="docFields.data"
            :show-edit="false"
            :additional-menu-items="[{
              label: 'aposPalette:resetPalettePosition',
              action: 'reset-position',
              emitEvent: true
            }]"
            @close="menuCloseHandler"
          />
       ...
    menuCloseHandler(_doc, action) {
      if (action === 'reset-position') {
        this.resetPosition();
      }
    }

If I pass emitEvent it will simply emit close with the action as parameter.

What are the specific steps to test this change?

See above

What kind of change does this PR introduce?

• Bug fix
• New feature
• Refactor
• Documentation
• Build-related changes
• Other

Make sure the PR fulfills these requirements:

• It includes a) the existing issue ID being resolved, b) a convincing reason for adding this feature, or c) a clear description of the bug it resolves
• The changelog is updated
• Related documentation has been updated
• Related tests have been updated

[linear]

PRO-6843 As a user, I want to be able to move Palette so that I can see elements that might be hidden under it to the right.

[boutell]

There is already a way to register additional context operations server side. The palette module can call:

self.apos.doc.addContextOperation({
  action: 'reset-palette-position',
  if: {
    type: self.__meta.name
  }  
});

This will make the operation available only for palette.

So there is no need to introduce a redundant way of registering custom context operations.

However I do think you may need a patch to allow them to trigger a bus event rather than opening a modal. This is the current logic that implements the "operation" property:

      const props = {
        moduleName: operation.moduleName || this.moduleName,
        // For backwards compatibility
        doc,
        ...docProps(doc),
        ...operation.props
      };
      await apos.modal.execute(operation.modal, props);

This will need an update to support emitting a bus event with an object containing the props as an alternative.

[boutell]

(Excuse me, self.__meta.name, which is just a cute way of saying this module's name, you could also hardcode the string)

[boutell]

Approving for time but please fix changelog

[boutell]

Change

[ValJed]

updated