Skip to content

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

Merged
wraithgar merged 1 commit into
latestfrom
owlstronaut/progress-fix
Jul 2, 2025
Merged

fix: ensure progress bars display consistently across all environments#8411
wraithgar merged 1 commit into
latestfrom
owlstronaut/progress-fix

Conversation

@owlstronaut

@owlstronautowlstronaut commented Jul 1, 2025

Copy link
Copy Markdown

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.

Fixesnpm/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 ownerJuly 1, 2025 19:32
Comment threadworkspaces/config/lib/definitions/definitions.js Outdated
@owlstronaut
owlstronautforce-pushed the owlstronaut/progress-fix branch from 1434cb3 to ed0e04bCompareJuly 1, 2025 21:57
@wraithgar

Copy link
Copy Markdown
Contributor

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
owlstronautforce-pushed the owlstronaut/progress-fix branch from ed0e04b to d2c92fdCompareJuly 2, 2025 15:39
@owlstronaut

owlstronaut commented Jul 2, 2025

Copy link
Copy Markdown
Author

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 latestJul 2, 2025
@wraithgar
wraithgar deleted the owlstronaut/progress-fix branch July 2, 2025 18:39
@github-actionsgithub-actionsBot 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.
Fixesnpm/statusboard#996
Sign up for freeto 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

@owlstronaut@wraithgar@alexsch01