Summary
Allowing for errors raised inside of bridge commands to be handled locally.
What is the feature request for?
discord.ext.bridge
The Problem
When writing bridge commands, no error handler can be directly attached to the command.
An error handler of such should look like this: @bridge_command_name.error
Currently, however, doing so raises the following error: AttributeError: 'BridgeCommand' object has no attribute 'error'
The Ideal Solution
The ideal solution is being able to have the same syntax as other types of commands where error handlers can be attached directly to the BridgeCommand. This would look the same way as the previous: @bridge_command_name.error
The Current Solution
The current solution is to handle all errors within the respective on_command_error and on_application_command_error events globally.
Additional Context
No response
Summary
Allowing for errors raised inside of bridge commands to be handled locally.
What is the feature request for?
discord.ext.bridge
The Problem
When writing bridge commands, no error handler can be directly attached to the command.
An error handler of such should look like this:
@bridge_command_name.errorCurrently, however, doing so raises the following error:
AttributeError: 'BridgeCommand' object has no attribute 'error'The Ideal Solution
The ideal solution is being able to have the same syntax as other types of commands where error handlers can be attached directly to the BridgeCommand. This would look the same way as the previous:
@bridge_command_name.errorThe Current Solution
The current solution is to handle all errors within the respective
on_command_errorandon_application_command_errorevents globally.Additional Context
No response