-
Notifications
You must be signed in to change notification settings - Fork 29
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(Canvas): Use path
+scope
as VizNode ID
#1699
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1699 +/- ##
============================================
+ Coverage 78.62% 78.84% +0.22%
Complexity 365 365
============================================
Files 439 465 +26
Lines 14234 14570 +336
Branches 2769 2792 +23
============================================
+ Hits 11191 11488 +297
+ Misses 2954 2813 -141
- Partials 89 269 +180 ☔ View full report in Codecov by Sentry. |
90f234f
to
548d4fa
Compare
Currently, the component name is being used as the title in the `CanvasForm`. This commit uses the corresponding `Title` property if available from components, eips and kamelets, and the `ID` as a last resort. fix: KaotoIO#1462 prerequisite of: KaotoIO#1699
Currently, the component name is being used as the title in the `CanvasForm`. This commit uses the corresponding `Title` property if available from components, eips and kamelets, and the `ID` as a last resort. fix: KaotoIO#1462 prerequisite of: KaotoIO#1699
Currently, the component name is being used as the title in the `CanvasForm`. This commit uses the corresponding `Title` property if available from components, eips and kamelets, and the `ID` as a last resort. fix: KaotoIO#1462 prerequisite of: KaotoIO#1699
Currently, the component name is being used as the title in the `CanvasForm`. This commit uses the corresponding `Title` property if available from components, eips and kamelets, and the `ID` as a last resort. fix: KaotoIO#1462 prerequisite of: KaotoIO#1699
Currently, the component name is being used as the title in the `CanvasForm`. This commit uses the corresponding `Title` property if available from components, eips and kamelets, and the `ID` as a last resort. fix: KaotoIO#1462 prerequisite of: KaotoIO#1699
548d4fa
to
021c488
Compare
Currently, the component name is being used as the title in the `CanvasForm`. This commit uses the corresponding `Title` property if available from components, eips and kamelets, and the `ID` as a last resort. fix: KaotoIO#1462 prerequisite of: KaotoIO#1699
18a712f
to
f0a3183
Compare
// Temporary workaround since the toolbar is updated but the config form is closed | ||
cy.openStepConfigurationTab('setHeader'); |
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.
This will be handled here: #1869
Currently, when transforming a flow into `VisualizationNodes`, the nodes `Id`s are randomly generated, causing that whenever there's a change in the structure of the flow, previous `Id`s change. This commit uses the `path` + `scope` so the `VisualizationNodes` IDs are stable between interacting with the flow.
f0a3183
to
03e7dfb
Compare
Quality Gate passedIssues Measures |
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 👍
Context
Currently, when transforming a flow into
VisualizationNodes
, the nodesId
s are randomly generated, causing that whenever there's a change in the structure of the flow, previousId
s change.Changes
This commit uses the
path
+scope
so theVisualizationNodes
IDs are stable between interacting with the flow.