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
Similar to the existing hook:onError event, which allows to add handlers on hook failures, we need a pipe:onError event, allowing users to plug handlers listening to pipe failures.
Example Use Case
Easily catch faulty pipes
Add dedicated logs on custom code executions
Possible Solution (optional)
That event should be triggered by the pipe wrapper, which is added to any and all pipes added by the plugins manager.
That event must be listened only by hooks: there is no sense allowing pipes to listen to that event.
The text was updated successfully, but these errors were encountered:
Feature Description
Similar to the existing
hook:onError
event, which allows to add handlers on hook failures, we need apipe:onError
event, allowing users to plug handlers listening to pipe failures.Example Use Case
Possible Solution (optional)
That event should be triggered by the pipe wrapper, which is added to any and all pipes added by the plugins manager.
That event must be listened only by hooks: there is no sense allowing pipes to listen to that event.
The text was updated successfully, but these errors were encountered: