Should the ?Issues command have an optional param to pull more details on an individual issue?

[theboxmage]

The code wouldn't be that hard to add an optional param to the Issues command.

Design Questions:

• Expected format?
• Same command or new one
• Any issues if I split the run method to have 2 helper methods to generate the embed and have run just send the returned embed?

Example syntax would be ?issues codesupport/discord-bot 37

[ajsaraujo]

In terms of usability, a single command is better. I mean...

# Different commands
?issue-by-id codesupport/discord-bot 37

# Same command
?issues codesupport/discord-bot 37

If we were to make two different commands, we could name them IssueCommand and IssuesCommand, it would keep the command name short, although it could also make things more confusing.

# 3 recentmost issues
?issues codesupport/discord-bot

# Get issue 37, must supply an issue id
?issue codesupport/discord-bot 37

I prefer having a single command. I also would like to leave the suggestion of adding issue as an alias for IssuesCommand if we choose to keep it in a single command.

I think that splitting the embed generation in two private methods is nice for readability, and the syntax you proposed is nice too.

[theboxmage]

Single command is fine to me, I forgot you could alias commands. I'll look into it.