smartcommit implements the config command, that is supposed to manipulate the config in some way it seems. At first it seems that smartcommit config edit must edit the config, and smartcommit config show should display the config (analogical to git config).
Although behaviour of smartcommit config show seems sane and expected, smartcommit config edit inexplicably edits the prompt not the config. If prompt is a part of the config, then why isn't config edited with smartcommit config edit? If it isn't a part of the config, then why in the hell it's edited with the smartcommit config edit? Makes no sense.
Proposed solution:
smartcommit config show would show the config with the prompt.smartcommit config edit would open the config.yaml file in the text editor.
This resolves the ambiguity, and lets the user to edit system prompt and config right where they belong.
smartcommit implements the
configcommand, that is supposed to manipulate the config in some way it seems. At first it seems thatsmartcommit config editmust edit the config, andsmartcommit config showshould display the config (analogical togit config).Although behaviour of
smartcommit config showseems sane and expected,smartcommit config editinexplicably edits the prompt not the config. If prompt is a part of the config, then why isn't config edited withsmartcommit config edit? If it isn't a part of the config, then why in the hell it's edited with thesmartcommit config edit? Makes no sense.Proposed solution:
smartcommit config showwould show the config with the prompt.smartcommit config editwould open theconfig.yamlfile in the text editor.This resolves the ambiguity, and lets the user to edit system prompt and config right where they belong.