Skip to content

📖 Fix WECS panel size inconsistency #2277

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.

Sign up for GitHub

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

Jump to bottom
Merged
btwshivam merged 2 commits into from
Dec 10, 2025
Merged

📖 Fix WECS panel size inconsistency #2277

btwshivam merged 2 commits into from
Dec 10, 2025
+1 −1

Conversation

@rahulshendre
Copy link
Contributor

@rahulshendre rahulshendre commented Dec 10, 2025 •
edited
Loading

Fixes the issue where the WECS details panel did not expand fully compared to staged workloads, it now does, keeping the UI consistent.

Fixes #2274

@github-actions
Copy link
Contributor

github-actions bot commented Dec 10, 2025

👋 Hello! @rahulshendre Welcome to the Kubestellar.

Thank you for submitting your first Pull Request to KubeStellar. We are delighted to have you in our Universe!
Please make sure to check out our Contribution Guide and feel free to join our Slack channel for any questions.

@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/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Dec 10, 2025
@kubestellar-prow
Copy link

kubestellar-prow bot commented Dec 10, 2025

Hi @rahulshendre. 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.

@rahulshendre rahulshendre mentioned this pull request Dec 10, 2025
Closed
1 task
@oksaumya
Copy link
Member

oksaumya commented Dec 10, 2025 •
edited
Loading

@rahulshendre include a video or images showing the changes before and after.

@rahulshendre
Copy link
Contributor Author

rahulshendre commented Dec 10, 2025

sure @oksaumya
Before (issue)

ui_inconsistency_issue.mp4

After (fixed)

ui_inconsistency_solved.mov

@Arpit529Srivastava
Copy link
Member

Arpit529Srivastava commented Dec 10, 2025

/ok-to-test

@kubestellar-prow kubestellar-prow bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Dec 10, 2025
kunal-511
kunal-511 reviewed Dec 10, 2025
View reviewed changes
Copy link
Member

@kunal-511 kunal-511 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rahulshendre Please run
npm run format

and then push your changes

@kunal-511
Copy link
Member

kunal-511 commented Dec 10, 2025

/lgtm
/approve

@kubestellar-prow kubestellar-prow bot added the lgtm Indicates that a PR is ready to be merged. label Dec 10, 2025
@kubestellar-prow
Copy link

kubestellar-prow bot commented Dec 10, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kunal-511

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

The pull request process is described 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

@kubestellar-prow
Copy link

kubestellar-prow bot commented Dec 10, 2025

LGTM label has been added.

DetailsGit tree hash: 2b2a1f07fea49a8f57302c8077b5767ae4a9666e

@kubestellar-prow kubestellar-prow bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 10, 2025
@github-project-automation github-project-automation bot moved this from In Progress to Ready to Merge in KubeStellar UI Project Dec 10, 2025
@btwshivam btwshivam merged commit 61fb70d into kubestellar:dev Dec 10, 2025
11 of 13 checks passed
@github-project-automation github-project-automation bot moved this from Ready to Merge to Done in KubeStellar UI Project Dec 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@kunal-511 kunal-511 kunal-511 left review comments

@btwshivam btwshivam btwshivam approved these changes

Assignees

@kunal-511 kunal-511

@btwshivam btwshivam

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. frontend lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

KubeStellar UI Project
Status: Done

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

[Bug]: Inconsistency in the details panel of the WECS

5 participants

@rahulshendre @oksaumya @Arpit529Srivastava @kunal-511 @btwshivam