Context
Some users would find very convenient to have a 'Trigger' option to manually trigger an existing link for reprocessing.
Today some are enabling / disabling the link as workaround to produce this action. The goals is be to simplify this behavior.
In our case some processing is done automatically, and not all widgets have a 'process' button to force reprocessing.
Proposed solutions
At the moment I see two approaches
Option 1: Add an action to default implementation
Ideally this could be part of the default implementation of SchemeEditWidget.
Here is an example of a diff that could create this.
Option 2: Expose require API of the context menu
An alternative could be to move the __contextMenuTarget and __linkMenu attributes to a less restrictive scope (ideally to public API) or provide a public API to reach it.
Next
I would be happy to provide a PR for any of the options (or a third alternative).
Please let me know which direction would be most acceptable to the maintainers.
Context
Some users would find very convenient to have a 'Trigger' option to manually trigger an existing link for reprocessing.
Today some are enabling / disabling the link as workaround to produce this action. The goals is be to simplify this behavior.
In our case some processing is done automatically, and not all widgets have a 'process' button to force reprocessing.
Proposed solutions
At the moment I see two approaches
Option 1: Add an action to default implementation
Ideally this could be part of the default implementation of
SchemeEditWidget.Here is an example of a diff that could create this.
Option 2: Expose require API of the context menu
An alternative could be to move the
__contextMenuTargetand__linkMenuattributes to a less restrictive scope (ideally to public API) or provide a public API to reach it.Next
I would be happy to provide a PR for any of the options (or a third alternative).
Please let me know which direction would be most acceptable to the maintainers.