We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add mention parameter to ApplicationCommand
The core library
There is no easy way to properly highlight an ApplicationCommand in a message.
The markdown has the format </COMMAND_NAME:APPLICATION_ID>
</COMMAND_NAME:APPLICATION_ID>
The solution would be to have a mention attribute for ApplicationCommands.
mention
@bot.application_command() async def command(ctx: ApplicationContext): await ctx.respond(ctx.command.mention)
The best way currently is to craft the markdown by hand every time.
@bot.application_command() async def command(ctx: ApplicationContext): await ctx.respond(f"</{ctx.command.name}:{ctx.bot.application_id}>")
As far as I see, the application_id is not accessible within the ApplicationCommand class, which is necessary for the markdown.
application_id
ApplicationCommand
The text was updated successfully, but these errors were encountered:
This was addressed in PR #1523 and has been added to the source code ever since
Sorry, something went wrong.
No branches or pull requests
Summary
Add mention parameter to ApplicationCommand
What is the feature request for?
The core library
The Problem
There is no easy way to properly highlight an ApplicationCommand in a message.
The markdown has the format
</COMMAND_NAME:APPLICATION_ID>
The Ideal Solution
The solution would be to have a
mention
attribute for ApplicationCommands.The Current Solution
The best way currently is to craft the markdown by hand every time.
Additional Context
As far as I see, the
application_id
is not accessible within theApplicationCommand
class, which is necessary for the markdown.The text was updated successfully, but these errors were encountered: