Skip to content

Commit

Permalink
Documentation improvements on bridge commands (Pycord-Development#1569)
Browse files Browse the repository at this point in the history
* Documentation improvements on bridge commands

* Update discord/ext/bridge/context.py

Co-authored-by: JustaSqu1d <overenchanted.gaming@gmail.com>

Co-authored-by: BobDotCom <71356958+BobDotCom@users.noreply.github.com>
Co-authored-by: JustaSqu1d <overenchanted.gaming@gmail.com>
  • Loading branch information
3 people authored Aug 16, 2022
1 parent 2c3f794 commit d5119eb
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion discord/ext/bridge/context.py
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ class BridgeContext(ABC):
this class are meant to give parity between the two contexts, while still allowing for all of their functionality.
When this is passed to a command, it will either be passed as :class:`BridgeExtContext`, or
:class:`BridgeApplicationContext`. Since they are two separate classes, it is quite simple to use :func:`isinstance`
:class:`BridgeApplicationContext`. Since they are two separate classes, it's easy to use the :attr:`BridgeContext.is_app` attribute.
to make different functionality for each context. For example, if you want to respond to a command with the command
type that it was invoked with, you can do the following:
Expand Down

0 comments on commit d5119eb

Please sign in to comment.