🐛 fix(ui): remove static dash from cluster name display

[sarafarajnasardi]

Remove CSS ::after pseudo-element that was adding an unwanted dash character to all react-flow nodes in the tree view. The rule was adding 'content: "-"' which appeared as a trailing dash after cluster names.

Fixes #2300

Description

Remove a CSS ::after pseudo-element that was adding an unwanted dash (-) to all React Flow nodes in the tree view. This resulted in a trailing dash being displayed after cluster names in both Staged Workloads and Deployed Workloads views.

This change ensures cluster names render cleanly without any unintended characters.

Related Issue

Fixes #2300

Changes Made

• Updated ...
• Refactored ...
• Fixed ...
• Added tests for ...

Checklist

Please ensure the following before submitting your PR:

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

Screenshots or Logs (if applicable)

before

after

Additional Notes

[kubestellar-prow]

[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 onkar717 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:

• OWNERS

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

[github-actions]

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:

• 📦 Quick Start
• 📖 Documentation
• 🎬 YouTube - Getting Started & Contributing

Contributor Resources:

• 📚 Contributor Handbook
• 🪜 Contributor Ladder
• 🎓 Mentorship Programs (LFX, GSoC)
• 💬 Slack - #kubestellar-dev

---

🌟 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]

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.