Fix/error handler#109
Draft
PenguinBoi12 wants to merge 2 commits into
Draft
Conversation
PenguinBoi12
force-pushed
the
fix/error-handler
branch
from
19a813b to
7054a6e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Error handlers (
@bot.error,@ext.error,@cmd.error) only matched the exact exception type, so handlers registered for a base class (or the default@bot.error()fallback) silently never fired for subclasses. Extension/bot-level command errorhandlers also never ran for exceptions raised inside a command body.
Additionally, once an error was handled, the command would still send a generic "usage: ..." message and log it as unhandled.
This PR:
Type of Change
Pre-merge Checklist
pytestmypy