Skip to content

Command "command" not found. #356

@jayvdb

Description

@jayvdb

We are regularly seeing Command "foo" not found. when the person correctly did corobo foo ....
They used the wrong arguments, but the error returned is confusing.
It should tell them they gave the foo command the wrong arguments, and possible even force feed them the help in a DM to help them use the bot properly.

What is happening is that corobo is not doing partial matches on only the command, but the error is saying that it cant match the command.

> corobo lmgtfy
@co-robo: Command "lmgtfy" not found.
> corobo lmgtfy foo
Hey! You seem to ...

lmgtfy was the command in normal parlance. foo is a parameter, or argument, etc.
The error message is wrong, and unhelpful.

Metadata

Metadata

Assignees

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions