Skip to content

Feat!: improve signal CLI UX #4812

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 5 commits into from
Jul 1, 2025
Merged

Feat!: improve signal CLI UX #4812

merged 5 commits into from
Jul 1, 2025

Conversation

georgesittas
Copy link
Contributor

@georgesittas georgesittas commented Jun 25, 2025

Current state of the CLI UX for signals on this branch:

image

@georgesittas georgesittas marked this pull request as draft June 25, 2025 17:12
@georgesittas georgesittas marked this pull request as ready for review June 30, 2025 19:39
@georgesittas georgesittas force-pushed the jo/signal_ux_improvements branch 2 times, most recently from df7ddfb to caacc77 Compare July 1, 2025 09:55
@georgesittas
Copy link
Contributor Author

Latest state of the PR looks like this in the CLI:

Non-verbose mode:

image

Very-verbose mode:

image

@georgesittas georgesittas requested a review from izeigerman July 1, 2025 09:57
tree.add(f"check: {check}")

ready = ", ".join(formatted_ready_intervals)
tree.add(f"[{color}]ready: {ready}[/{color}]")
Copy link
Contributor

Choose a reason for hiding this comment

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

Currently, the legend is always ready and its actual status is conveyed through colour. Personally, along with the corresponding colours I’d prefer more explicit messaging for the three cases as well for example:

  • All intervals ready
  • Some intervals unready
  • No intervals ready

and then list which intervals are ready below. It’s a minor preference, but relying solely on colour feels a bit implicit, especially from an accessibility perspective and distinguishing green and yellow in some terminals

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'd be curious to hear @sungchun12's take on this. I hear you, esp. the bit regarding accessibility. I think trying to improve the messaging may be the better thing here.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated:

Non-verbose mode:
Screenshot 2025-07-01 at 7 06 24 PM

Very-verbose mode:
Screenshot 2025-07-01 at 7 06 35 PM

Copy link
Contributor

Choose a reason for hiding this comment

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

Aligned with the new images

@georgesittas georgesittas force-pushed the jo/signal_ux_improvements branch from 9bd9e05 to 0634bbc Compare July 1, 2025 13:40
@georgesittas georgesittas changed the title Feat: improve signal CLI UX Feat!: improve signal CLI UX Jul 1, 2025
@georgesittas georgesittas force-pushed the jo/signal_ux_improvements branch 2 times, most recently from 2bec393 to 2a08f0f Compare July 1, 2025 13:55
duration: float,
) -> None:
"""Updates the signal checking progress."""
tree = Tree(f"[{signal_idx + 1}/{total_signals}] {signal_name} {duration:.2f}s")
Copy link
Contributor Author

@georgesittas georgesittas Jul 1, 2025

Choose a reason for hiding this comment

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

I'm leaving the right-justification of the duration for a followup PR (if we think it's worth it), as it will require some width calculations similar to what we do in the evaluation stage.

@georgesittas georgesittas force-pushed the jo/signal_ux_improvements branch from 7ebfaea to 54ced6e Compare July 1, 2025 16:06
@georgesittas georgesittas force-pushed the jo/signal_ux_improvements branch from 98754b2 to d0285d3 Compare July 1, 2025 16:19
@georgesittas georgesittas linked an issue Jul 1, 2025 that may be closed by this pull request
@georgesittas georgesittas enabled auto-merge (squash) July 1, 2025 16:20
@georgesittas georgesittas merged commit 9899243 into main Jul 1, 2025
26 of 27 checks passed
@georgesittas georgesittas deleted the jo/signal_ux_improvements branch July 1, 2025 16:32
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.

Feature: Signals print if triggered vs. not during runs
4 participants