Skip to content

fix: ensure progress bars display consistently across all environments #8411

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

Merged
merged 1 commit into from
Jul 2, 2025

Conversation

owlstronaut
Copy link
Contributor

@owlstronaut owlstronaut commented Jul 1, 2025

The progress configuration's default value and runtime behavior now use
identical logic, preventing cases where progress bars were unexpectedly
disabled in cloud IDEs and other environments.

Fixes npm/statusboard#996

@owlstronaut owlstronaut marked this pull request as ready for review July 1, 2025 19:32
@owlstronaut owlstronaut requested a review from a team as a code owner July 1, 2025 19:32
@owlstronaut owlstronaut force-pushed the owlstronaut/progress-fix branch from 1434cb3 to ed0e04b Compare July 1, 2025 21:57
@wraithgar
Copy link
Member

Ok after a deep dive with boolean tables and everything the logic should be: !(ci || !tty || dumb)

This will properly short circuit if we are in CI, or if we're not a TTY, and set display appropriately for all 3 conditions.

@owlstronaut owlstronaut force-pushed the owlstronaut/progress-fix branch from ed0e04b to d2c92fd Compare July 2, 2025 15:39
@owlstronaut
Copy link
Contributor Author

owlstronaut commented Jul 2, 2025

Ok after a deep dive with boolean tables and everything the logic should be: !(ci || !tty || dumb)

This will properly short circuit if we are in CI, or if we're not a TTY, and set display appropriately for all 3 conditions.

Just pushed for that. So same thing but with shortcut advantage 😄 I'm still not completely convinced it is actually different, lol

@wraithgar wraithgar merged commit 5b858c6 into latest Jul 2, 2025
33 checks passed
@wraithgar wraithgar deleted the owlstronaut/progress-fix branch July 2, 2025 18:39
@github-actions github-actions bot mentioned this pull request Jul 2, 2025
reggi pushed a commit that referenced this pull request Jul 9, 2025
#8411)

The progress configuration's default value and runtime behavior now use
identical logic, preventing cases where progress bars were unexpectedly
disabled in cloud IDEs and other environments.

Fixes npm/statusboard#996
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG] progress config defaults based on CI but flatOptions based on tty
3 participants