public class CommandUsageException extends CommandFailedException
CommandFailedException
thrown when a command fails because it is called incorrectly.
This exception is an indication of a developer error, not a user error. In practice, these exceptions should never occur during normal operation.
Developer note: When considering the command
against the usage
message, be
aware that representing the command as a single String
may conceal subtle usage issues. For example, when
providing multiple arguments to a command builder
via its
argument(String)
, providing multiple arguments in a
single call separated by spaces will result in the arguments not being received correctly by the command when it is
executed but will produce the same String
representation. For example, both of the following will produce the
same String
:
builder.command("command").argument("a b").build(...).call();
builder.command("command").argument("a").argument("b").build(...).call();
However, the executed command will receive different arguments ("a b"
and ["a", "b"]
, respectively).
If the command arguments appear to be valid based on the usage message, double-check how they are provided.Constructor and Description |
---|
CommandUsageException(KeyedMessage message,
String command,
String usage) |
Modifier and Type | Method and Description |
---|---|
String |
getCommand() |
String |
getUsage() |
getKeyedMessage, getLocalizedMessage, getMessageKey
addSuppressed, fillInStackTrace, getCause, getMessage, getStackTrace, getSuppressed, initCause, printStackTrace, printStackTrace, printStackTrace, setStackTrace, toString
Copyright © 2022 Atlassian. All rights reserved.