Repository navigation
Refactor level-control command registration for clarity - #25
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request refactors the command registration logic in
LevelControlCommandto improve clarity and maintainability. The changes separate the construction of each subcommand into individual variables before assembling them under the root command. Additionally, there are minor documentation and formatting updates.Command registration refactoring:
registermethod inLevelControlCommandto build each subcommand (level-up,set-level,status,status-other,configure) separately as variables, then compose them under the rootlevel-controlcommand for clearer structure and easier future modifications. [1] [2]Documentation and formatting:
unrecognised→unrecognized) inConfigureCommand.ConfigureCommandfor consistency. [1] [2]