feat: refactored panel names #30
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bakayu
approved these changes
Oct 15, 2025
bakayu
added
the
hacktoberfest-accepted
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #29
Title: Refactor: Centralize Panel Name Definitions and Update Mapping
Description:
This pull request introduces a small but important refactor around how panel names are managed and displayed throughout the application.
Changes Made:
Added centralized constants for panel names (panelZero through panelSix) to improve maintainability and avoid hard-coded strings.
Updated the titles map to use the new panel name constants.
Ensured consistent labeling across all panels including Main, Status, Files, Branches, Commits, Stash, and Logs.
Minor fix to ensure ANSI escape codes are stripped properly using ansiRegex (already present, but included for clarity).
Why:
Improves readability and maintainability of panel name assignments.
Reduces the risk of typos and inconsistencies in panel naming across the codebase.
Makes it easier to update panel labels in the future by changing a single source of truth.
Please review and let me know if any naming conventions or panel mappings should be adjusted further.