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
Currently onChange events are handled through callbacks, which is fine for most use-cases. However implementing these functions to return RxJS observables would allow better reactive programming style and usage of the powerful RxJS Operators.
With function overloads you could still provide backwards-compatibility to leave the choice to the extension developer to use either observables or callbacks. With the only downside being RxJS an additional dependency to this SDK.
Currently onChange events are handled through callbacks, which is fine for most use-cases. However implementing these functions to return RxJS observables would allow better reactive programming style and usage of the powerful RxJS Operators.
With function overloads you could still provide backwards-compatibility to leave the choice to the extension developer to use either observables or callbacks. With the only downside being RxJS an additional dependency to this SDK.
Here is a code example with observables referencing to the Initiative Tracker extension example:
Using observable instead of callback
Example with RxJS map-operator
The text was updated successfully, but these errors were encountered: