Skip to content

Refactor: Use KEY_HINTS constants in wizard apps#44

Closed
FL4TLiN3 wants to merge 1 commit intomainfrom
refactor/use-key-hints-in-wizards
Closed

Refactor: Use KEY_HINTS constants in wizard apps#44
FL4TLiN3 wants to merge 1 commit intomainfrom
refactor/use-key-hints-in-wizards

Conversation

@FL4TLiN3
Copy link
Contributor

@FL4TLiN3 FL4TLiN3 commented Dec 4, 2025

Summary

  • Add QUIT, ESC_BACK, and CONFIRM constants to KEY_HINTS in constants.ts
  • Replace hardcoded key hint strings in apps/status/app.tsx, apps/tag/app.tsx, and apps/unpublish/app.tsx with KEY_HINTS constants
  • Ensure consistent hint format across all wizard apps (space-separated key:Action format)

Closes #40

Test plan

  • Verify status wizard displays correct key hints
  • Verify tag wizard displays correct key hints
  • Verify unpublish wizard displays correct key hints

Note

Replace hardcoded key hint text in status/tag/unpublish wizards with KEY_HINTS and add QUIT, ESC_BACK, and CONFIRM constants.

  • TUI
    • Constants (packages/tui/src/constants.ts): Add KEY_HINTS.QUIT, KEY_HINTS.ESC_BACK, KEY_HINTS.CONFIRM for standardized keyhint labels.
    • Wizard Apps:
      • packages/tui/apps/status/app.tsx: Replace inline key-hint strings with KEY_HINTS constants.
      • packages/tui/apps/tag/app.tsx: Use KEY_HINTS for confirm/back/quit hints; maintain ctrl+q note.
      • packages/tui/apps/unpublish/app.tsx: Use KEY_HINTS for navigation/select/back/quit hints.
    • Ensures consistent key:Action hint format across wizard screens.

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

@vercel
Copy link

vercel bot commented Dec 4, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
perstack Ready Ready Preview Comment Dec 4, 2025 6:59am

@codecov
Copy link

codecov bot commented Dec 4, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

)}
<Box marginTop={1}>
<Text dimColor>↑↓ navigate · enter select · esc back · q quit</Text>
<Text dimColor>{`${KEY_HINTS.NAVIGATE} ${KEY_HINTS.SELECT} ${KEY_HINTS.ESC_BACK} ${KEY_HINTS.QUIT}`}</Text>
Copy link

Choose a reason for hiding this comment

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

Bug: Incomplete refactoring creates inconsistent hint formats within wizards

The refactoring to use KEY_HINTS constants is incomplete. The shared components WizardExpertSelector and VersionSelector still display hints in the old format (↑↓ navigate · enter select · q quit), while the app-specific components now use the new format (↑↓:Navigate Enter:Select Esc:Back q:Quit). This creates an inconsistent user experience within the same wizard flow, directly contradicting the PR's goal to "ensure consistent hint format across all wizard apps."

Additional Locations (2)

Fix in Cursor Fix in Web

@FL4TLiN3 FL4TLiN3 closed this Dec 4, 2025
@FL4TLiN3 FL4TLiN3 deleted the refactor/use-key-hints-in-wizards branch December 8, 2025 19:11
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.

Refactor: Use KEY_HINTS constants in wizard apps

1 participant