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
This is a bug report/feature request/support request/change request
Problem
The subscribe function for filter accepts either a single decoder or an array of decoders. This leads to a lot of overhead for the library consumer when handling the response: it might fail before even attempting a subscription, all subscriptions requests might fail, some might fail and some succeed, or all succeed. It's cleaner for the function to accept a single decoder and respond with a single failure or success.
Proposed Solutions
Refactor subscribe function in filter to only accept a single decoder
Notes
The text was updated successfully, but these errors were encountered:
This issue proposes a solution to the problem of ambiguity of error handling when we don't have fail or not fail which happens because of a need to provide support to multiple decoders.
@vpavlin@hackyguru do you think we should continue supporting ability to subscribe to multiple decoders?
This is a bug report/feature request/support request/change request
Problem
The subscribe function for filter accepts either a single decoder or an array of decoders. This leads to a lot of overhead for the library consumer when handling the response: it might fail before even attempting a subscription, all subscriptions requests might fail, some might fail and some succeed, or all succeed. It's cleaner for the function to accept a single decoder and respond with a single failure or success.
Proposed Solutions
Refactor subscribe function in filter to only accept a single decoder
Notes
The text was updated successfully, but these errors were encountered: