Skip to content

Conversation

@JulienVannier66
Copy link
Contributor

@JulienVannier66 JulienVannier66 commented Jan 28, 2026

What does this PR do?

Support zero values for skins in the OSS::ProgressBar

What are the observable changes?

Screenshot from 2026-01-28 18-25-15
Screencast.from.2026-01-29.09-49-52.webm

Good PR checklist

  • Title makes sense
  • Is against the correct branch
  • Only addresses one issue
  • Properly assigned
  • Added/updated tests
  • Added/updated documentation
  • Migrated touched components to Glimmer Components
  • Properly labeled

Note

Low Risk
Small template-only rendering change plus test/demo updates; minimal behavior impact outside the 0%-skins edge case.

Overview
Ensures OSS::ProgressBar correctly renders a multi-skin bar when all @skins values sum to 0 by 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 @value usage when @skins is provided.

Written by Cursor Bugbot for commit 61f35aa. This will update automatically on new commits. Configure here.

Copy link

@cursor cursor bot left a 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}} />`);
Copy link
Member

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 ?

Copy link
Contributor Author

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.

@JulienVannier66 JulienVannier66 merged commit 0ae6286 into master Jan 29, 2026
4 checks passed
@JulienVannier66 JulienVannier66 deleted the jv/support-zero-values-skins-progress-bar branch January 29, 2026 13:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants