SettingCommand cleanup #7

Closed
opened 2022-03-29 09:22:25 +00:00 by oko · 1 comment
Owner

The new settings functionality is great - though, it's a bit silly it uses 4 seperate commands.

Wouldnt it be more intuitive (and easier to maintain?) if the settings command was consolidated into subcommands?

Under this model, the setting command would be as follows:

  • setting
    • list (replaces settings)
    • get (replaces setting)
    • set (replaces setting_set)
    • reset (replaces setting_clear)

Im requesting feedback on this.

The new settings functionality is great - though, it's a bit silly it uses 4 seperate commands. Wouldnt it be more intuitive (and easier to maintain?) if the settings command was consolidated into subcommands? Under this model, the `setting` command would be as follows: + `setting` + `list` (replaces `settings`) + `get` (replaces `setting`) + `set` (replaces `setting_set`) + `reset` (replaces `setting_clear`) Im requesting feedback on this.
oko added this to the Kiafumi 1.0 milestone 2022-03-29 09:22:25 +00:00
oko added the
enhancement
label 2022-03-29 09:22:25 +00:00

All under a subcommand now.

All under a subcommand now.
Laika closed this issue 2022-03-29 16:09:41 +00:00
Laika added this to the Kiafumi Functionality project 2022-04-04 07:32:53 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: oko/kiafumi#7
No description provided.