feat: improve data export destination graph - #6073
Conversation
|
|
Running ultrareview automatically — This PR introduces a new destination editor with write-only header handling, grouping logic, and a large UI refactor. Bugs here could leak stored header values or corrupt destination configuration, warranting a deep multi-pass review.. I'll post findings when complete. |
There was a problem hiding this comment.
Ultrareview completed in 7m 21s
All reported issues were addressed across 5 files
Reply with feedback, questions, or to request a fix.
Fix all with cubic | Re-trigger cubic
There was a problem hiding this comment.
All reported issues were addressed across 6 files (changes from recent commits).
Tip: Review your code locally with the cubic CLI to iterate faster.
Fix all with cubic | Re-trigger cubic

Summary
Motivation
The export graph duplicated collectors when multiple data sources sent to the same destination. Destinations also had no direct editing path, which forced users to recreate configuration instead of maintaining the shared collector in place.
Summary by cubic
Groups export routes by destination so a shared collector renders once with converging connections, and makes source and destination nodes clickable with a new destination editor. Previously each route rendered its own destination node and destinations had no in-place editing path.
Details
Written for commit a7c09fb. Summary will update on new commits.