Skip to content

fix: ensure tree view edges are always visible#2413

Open
sarafarajnasardi wants to merge 2 commits intokubestellar:devfrom
sarafarajnasardi:#2279
Open

fix: ensure tree view edges are always visible#2413
sarafarajnasardi wants to merge 2 commits intokubestellar:devfrom
sarafarajnasardi:#2279

Conversation

@sarafarajnasardi
Copy link

Fix: Tree View Connecting Lines Not Visible

Fixes an issue where connecting lines (edges) between parent and child nodes were not rendered in the tree view on both Staged Workloads and Deployed Workloads pages.


Description

Connecting lines between tree nodes were not visible due to edge creation being conditionally gated by the isExpanded state. This caused edges to not be created when the tree was in its default or collapsed state, even though the nodes themselves were visible.

This PR removes the unnecessary conditional logic and ensures edges are always created between visible parent and child nodes. It also improves edge visibility by switching from low-opacity gradient strokes to solid colors and cleans up unused parameters.


Related Issue

Fixes #2279


Changes Made

  • Remove isExpanded conditional from edge creation in TreeViewNodes.tsx and WecsTopology.tsx
  • Ensure edges render correctly in both collapsed and expanded view modes
  • Change edge stroke styles from gradients to solid colors for better visibility
  • Remove unused isExpanded parameter from useTreeViewNodes hook
  • Clean up related logic for improved readability and maintainability

Checklist

  • I have reviewed the project's contribution guidelines.
  • I have tested the changes locally and ensured they work as expected.
  • My code follows the project's coding standards.
  • I have written unit tests for the changes (not applicable for UI-only changes).
  • I have updated the documentation (not applicable).

Screenshots or Logs (if applicable)

Before
No connecting lines visible between parent and child nodes
Screenshot From 2026-02-07 10-58-49

After
Connecting lines are clearly visible and correctly rendered between context → namespaces → resources
Screenshot From 2026-02-07 17-51-56

@kubestellar-prow kubestellar-prow bot added the dco-signoff: no Indicates the PR's author has not signed the DCO. label Feb 7, 2026
@kubestellar-prow
Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign clubanderson for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@github-actions
Copy link
Contributor

github-actions bot commented Feb 7, 2026

Welcome to KubeStellar! 🚀 Thank you for submitting this Pull Request.

Before your PR can be merged, please ensure:

DCO Sign-off - All commits must be signed off with git commit -s to certify the Developer Certificate of Origin

PR Title - Must start with an emoji: ✨ (feature), 🐛 (bug fix), 📖 (docs), 🌱 (infra/tests), ⚠️ (breaking change)

Getting Started with KubeStellar:

Contributor Resources:


🌟 Help KubeStellar Grow - We Need Adopters!

Our roadmap is driven entirely by adopter feedback. Whether you're using KubeStellar yourself or know someone who could benefit from multi-cluster Kubernetes:

📋 Take our Multi-Cluster Survey - Share your use cases and help shape our direction!


A maintainer will review your PR soon. Feel free to ask questions in the comments or on Slack!

@kubestellar-prow
Copy link

Hi @sarafarajnasardi. Thanks for your PR.

I'm waiting for a kubestellar member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@kubestellar-prow kubestellar-prow bot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Feb 7, 2026
- Remove isExpanded conditional from edge creation in TreeViewNodes and WecsTopology
- Edges now render correctly in both collapsed and expanded view modes
- Change edge stroke from gradients to solid colors for better visibility
- Remove unused isExpanded parameter from useTreeViewNodes hook

Fixes connecting lines not appearing between parent-child nodes in tree views

Signed-off-by: Sarafaraj Nasardi <[email protected]>
@kubestellar-prow kubestellar-prow bot added dco-signoff: yes Indicates the PR's author has signed the DCO. and removed dco-signoff: no Indicates the PR's author has not signed the DCO. labels Feb 7, 2026
- Remove isExpanded conditional from edge creation in TreeViewNodes and WecsTopology
- Edges now render correctly in both collapsed and expanded view modes
- Change edge stroke from gradients to solid colors for better visibility
- Remove unused isExpanded parameter from useTreeViewNodes hook

Fixes connecting lines not appearing between parent-child nodes in tree views

Signed-off-by: Sarafaraj Nasardi <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dco-signoff: yes Indicates the PR's author has signed the DCO. frontend needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

[Bug]: connecting lines between objects missing in tree view

1 participant