You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 23, 2024. It is now read-only.
There should be a difference in the events when running commands in case they error.
Currently, if a command errors, the commandError and commandExecute events will trigger.
This issue suggests that instead:
Any command run triggers the: commandTriggered event before running the command, then if the command runs successfully it should fire the commandExecuted event, otherwise it should fire the commandError event.
The text was updated successfully, but these errors were encountered:
⚡ Describe the New Feature
There should be a difference in the events when running commands in case they error.
Currently, if a command errors, the
commandError
andcommandExecute
events will trigger.This issue suggests that instead:
Any command run triggers the:
commandTriggered
event before running the command, then if the command runs successfully it should fire thecommandExecuted
event, otherwise it should fire thecommandError
event.The text was updated successfully, but these errors were encountered: