-
Notifications
You must be signed in to change notification settings - Fork 33.7k
fix(editor): Maintain back button when installing community nodes #16069
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
fix(editor): Maintain back button when installing community nodes #16069
Conversation
This prevents the back button from disappearing
Since official community nodes are now part of mergedNodes, we need to alert the view stack to update
Codecov ReportAll modified and coverable lines are covered by tests ✅ 📢 Thoughts on this report? Let us know! |
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.
cubic found 1 issue across 2 files. Review it in cubic.dev
React with 👍 or 👎 to teach cubic. Tag @cubic-dev-ai
to give specific feedback.
packages/frontend/editor-ui/src/components/Node/NodeCreator/Panel/CommunityNodeDetails.vue
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.
I tested locally as well and it works 🎉
✅ All Cypress E2E specs passed |
Got released with |
Summary
Maintain back button when installing community nodes. The problem was that verified official community nodes are now part of the
visibleNodeTypes
(see https://linear.app/n8n/issue/NODE-3009/distinguish-official-verified-nodes-from-community-built-ones) and we weren't updatingmergedNodes
, which is derived fromvisibleNodeTypes
.Updating
mergedNodes
has to be done manually since the root view stack only passes themergedNodes
as a value (ie: It is not aref
orcomputed
). Without doing a manual update, the problem would only be solved for unofficial verified nodes. Hence, we need to manually update the stack to solve the problem for both unofficial verified community nodes and official verified community nodes.We do not need to worry about unverified nodes because they are not in Strapi, and they do not get displayed in the Node Creator panel.
Related Linear tickets, Github issues, and Community forum posts
https://linear.app/n8n/issue/NODE-3034/when-installing-an-official-verified-node-on-1941-and-above-the-nodes
Review / Merge checklist
release/backport
(if the PR is an urgent fix that needs to be backported)