export: Improve error message consistency

Remove literal text "subcommand" from error messages. Most other
commands report errors like "<command> <subcommand> <message>", where
the message does not include the literal text "subcommand". The `export`
command was one of two exceptions to this.
This commit is contained in:
Matthew Woehlke
2025-12-01 14:08:56 -05:00
parent 91d7d19a89
commit 61143d7cef
6 changed files with 19 additions and 21 deletions

View File

@@ -270,8 +270,8 @@ static bool HandleExportMode(std::vector<std::string> const& args,
}
if (!unknownArgs.empty()) {
status.SetError("EXPORT subcommand given unknown argument: \"" +
unknownArgs.front() + "\".");
status.SetError("EXPORT given unknown argument: \"" + unknownArgs.front() +
"\".");
return false;
}
@@ -384,8 +384,8 @@ static bool HandleSetupMode(std::vector<std::string> const& args,
SetupArguments arguments = parser.Parse(args, &unknownArgs);
if (!unknownArgs.empty()) {
status.SetError("SETUP subcommand given unknown argument: \"" +
unknownArgs.front() + "\".");
status.SetError("SETUP given unknown argument: \"" + unknownArgs.front() +
"\".");
return false;
}