Releases: Kenny2github/discord-ext-slash
Releases · Kenny2github/discord-ext-slash
0.3.0 Prerelease 3
Fixes
- Forthport changes from 0.2.2
- More annotations
- Clean up
0.3.0 Prerelease 2
Fixes
in_addition
is removed, so remove it from the demoslash.__all__
is now defined- Support forward reference annotations
- The message of the
ValueError
raised when no argument is annotated withContext
was written when that was still namedSlashContext
0.3.0 Prerelease 1
New Stuff
@Group.default
on top of@Group.slash_cmd()
marks a subcommand as the one called when the base group is invoked.
Changes
default
behavior is fully clarified now, but not currently enabled.- This means
Option.default
is fully removed now. - Since calling a base group translates into calling the
default
subcommand, theGroup.coro
is now deprived of an original jurisdiction. Final behavior is that all parent coros will be called in order of increasing child levels before the command is invoked.
Fixes:
- Actual Python annotations for classes, instead of just doc descriptions
0.2.2
Major Fixes
- Because Group now inherits from Command, and all Groups were being instance-checked as Command first, subcommands ended up never being called... Switched the order.
- The stock check couldn't accept the self argument, so cog commands all failed.
0.2.1
New Stuff
slash.Context
subclasses can now be used to annotate the context argument. They will be instantiated with the same signature as the base class.
Changes
- Disabled
default
argument toOption
. It will now always beFalse
. The argument is not supported yet. The library will receive another update when it becomes supported.
0.2.0
New Stuff
- Base command groups will be able to be invoked directly at some point in the future, so that is supported now
- This means that the decorated coro is actually the callback
- Checks have been moved into
@Group.check
- You can specify
in_addition=True
to call the group callback before a subcommand callback MessageFlags
enum marks message flags- In particular,
MessageFlags.EPHEMERAL
can be passed into the newflags
argument inContext.respond()
to send a message à la Clyde that is private and dismissable
Changes
- The entire traceback for failed fetches when constructing
Context
s is no longer logged, only the fact that the fetch failed. - Some objects now have
__repr__
s or__str__
s Group
inherits fromCommand
Fixes
- Logger name was wrong (correct is
discord.ext.slash
) allowed_mentions
was actually supported by the API this whole time, but my implementation was faulty
0.1.4
Changes
- The
cog_check
method of a cog is now supported (though only as an async method)
Fixes
SlashBot.debug_guild
wasn't being casted toint
, and it was being set before callingsuper()
content
is now blindly casted tostr
0.1.3
Changes
- Cogs are actually a thing now, more or less.
Command.cog
,Group.cog
,Context.cog
have values now.
This was done because instance methods weren't being called with aself
argument- Groups copy their cog to their subcommands
Context.respond()
now takesembed
as shorthand for one-itemembeds
Fixes
- Options with names other than the function argument name used to break.
- Subcommands with no arguments used to not be callable.
- Critical: Not specifying a guild ID led to failure to register the command
- Subcommands in cogs were being doubly added as top-level commands
- If one command is invalid, this doesn't prevent the rest from being registered
0.1.2
A few bugfixes
id
s were notint
s in a lot of places.- Processing
Context.options
did not have error handling. - It turns out that
Choice.value
cannot beint
. - Changed doc of
Command
to say "parameters" becausecheck
is not an attribute
0.1.1
Fix README and consolidate decorator/add methods.