Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Documentation improvements on bridge commands #1569

Merged
merged 3 commits into from
Aug 16, 2022
Merged

Documentation improvements on bridge commands #1569

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ffb0b5b
Documentation improvements on bridge commands
UP929312 Aug 16, 2022
5e0e268
Update discord/ext/bridge/context.py
BobDotCom Aug 16, 2022
90bd9b7
Merge branch 'master' into patch-6
BobDotCom Aug 16, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion discord/ext/bridge/context.py
View file
Open in desktop
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