-
Notifications
You must be signed in to change notification settings - Fork 8.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(editor): Node creator actions #4696
Conversation
# Conflicts: # packages/editor-ui/src/components/Node/NodeCreator/CategorizedItems.vue
…ver globalLinkActions to composable
…to categorized items
… fix API actions display and prevent dragging of action nodes
…odes for the trigger helper panel, minor fixes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good, left some minor comments
packages/design-system/src/components/N8nNodeCreatorNode/NodeCreatorNode.vue
Outdated
Show resolved
Hide resolved
packages/design-system/src/components/N8nNodeCreatorNode/NodeCreatorNode.vue
Outdated
Show resolved
Hide resolved
packages/editor-ui/src/components/Node/NodeCreator/TriggerHelperPanel.vue
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Forgot to approve last time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
@MiloradFilipovic I goofed up and forgot to fix the breaking e2e tests. Should be all green now. Can you approve once more, please? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tests look good.
…es added from trigger panel
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
* master: fix: Use license-sdk v1.6.1 (#4872) feat(editor): Node creator actions (#4696) test(editor): Set e2e test retries (#4870) fix: Increase workflow reactivation max timeout to 1 day (#4869) fix: Stop returning `UNKNOWN ERROR` in the response if an actual error message is available (#4859) fix: Issue listing executions with Postgres (#4856) test(editor): Fix flaky e2e tests (#4779) fix: Use the same entrypoint for custom docker images as for the other images (no-changelog) (#4849) refactor: Deprecate `alwaysOpenEditWindow` for `string` (#4839) fix: Upgrade sse-channel to mitigate CVE-2019-10744 (#4835) # Conflicts: # packages/editor-ui/src/App.vue # packages/editor-ui/src/views/NodeView.vue
* feature/undo-redo: ⚡ Fixing tracking new nodes after latest merge ⚡ Fixing undo for moving connections ⚡ Fixing recording when moving nodes fix: Use license-sdk v1.6.1 (#4872) feat(editor): Node creator actions (#4696) test(editor): Set e2e test retries (#4870) ⚡ Fix for not clearing redo stack on every user action fix: Increase workflow reactivation max timeout to 1 day (#4869) 👌 Implemented command comparing logic 👌 Moving undo logic for disabling nodes to `NodeView` 👌 Addressing PR comments part 1 fix: Stop returning `UNKNOWN ERROR` in the response if an actual error message is available (#4859) fix: Issue listing executions with Postgres (#4856) test(editor): Fix flaky e2e tests (#4779) fix: Use the same entrypoint for custom docker images as for the other images (no-changelog) (#4849) refactor: Deprecate `alwaysOpenEditWindow` for `string` (#4839) fix: Upgrade sse-channel to mitigate CVE-2019-10744 (#4835) # Conflicts: # cypress/e2e/7-workflow-actions.cy.ts # cypress/pages/workflow.ts
Got released with |
This PR implements categorization and display of node actions. Actions are visible when accessed via the "On App Event" node creator item from the trigger helper panel.
After clicking the action, we add a node to the canvas with prefilled fields corresponding to the action config. Because we're merging regular/trigger nodes, if the added action is from the regular node, we also add a Manual trigger.
Part of this PR is also unifying the names of the node overrides as requested by the product/design.
Categorization
Actions are categorized into two categories.
Resource actions(regular nodes)
To get these categories, we iterate over the resource options property of a node and create a category for each property. We then look for operations that correspond to this resource. To map the operation to the resource, we use
displayOptions
property which indicates if the operation option is relevant to the resource.Recommended category(trigger nodes)
We check for the following properties in node config: 'event,' 'events,' and 'trigger on.' If any of these three exists, we take its options and parse them as recommended actions.
CleanShot.2022-11-30.at.15.32.01.mp4