-
Notifications
You must be signed in to change notification settings - Fork 3
Support zero values for skins in the OSS::ProgressBar #629
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
Support zero values for skins in the OSS::ProgressBar #629
Conversation
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.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
This is the final PR Bugbot will review for you during this billing cycle
Your free Bugbot reviews will reset on February 28
Details
Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.
To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.
|
|
||
| test('if the value is defined, the progress bar has the correct pending value', async function (assert) { | ||
| await render(hbs`<OSS::ProgressBar @value={{this.checkedValue}} @skins={{this.skins}} />`); | ||
| await render(hbs`<OSS::ProgressBar @skins={{this.skins}} />`); |
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.
we are removing the @value argument as it isn't used when using "skin-mode" right ?
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.
Yes, @skins type is skins?: Partial<Record<ProgressBarSkins, number>>;. This is due to a copy/paste error when writing the tests for @skins. When passing @skins, the @value is not read.
What does this PR do?
Support zero values for skins in the OSS::ProgressBar
What are the observable changes?
Screencast.from.2026-01-29.09-49-52.webm
Good PR checklist
Note
Low Risk
Small template-only rendering change plus test/demo updates; minimal behavior impact outside the 0%-skins edge case.
Overview
Ensures
OSS::ProgressBarcorrectly renders a multi-skin bar when all@skinsvalues sum to0by outputting a single empty segment instead of rendering no segments.Updates the visual dummy page with explicit 0% multi-segment examples, and adjusts/extends integration tests (including a new assertion for the 0% empty-bar style) while removing unnecessary
@valueusage when@skinsis provided.Written by Cursor Bugbot for commit 61f35aa. This will update automatically on new commits. Configure here.