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
Based on the fact that decoder is a primitive we use always in pair with Filter and it has knowledge on the pubsubTopic/contentTopic etc - we should use it.
const{ error, subscription }=awaitnode.filter.createSubscription(decoder);awaitsubscription.subscribe(callback);// or instead of createSubscription we can use subscribe APIconst{ error, subscription }=awaitnode.filter.subscribe(decoder,callback);awaitsubscription.subscribe(callback);
Also it doesn't seems to be used with many of other decoders and since one of the requirements is to have all decoders that are provided to use the same pubsubTopic - in that case we can just have one subscription per.
This is a feature request
Problem
From #2022 it seems that Filter API is hard-to-understand right now as it makes us do:
Proposed Solutions
Based on the fact that
decoder
is a primitive we use always in pair with Filter and it has knowledge on thepubsubTopic
/contentTopic
etc - we should use it.Also it doesn't seems to be used with
many
of other decoders and since one of the requirements is to have all decoders that are provided to use the samepubsubTopic
- in that case we can just have one subscription per.Notes
Additional context - #1981
The text was updated successfully, but these errors were encountered: