Operator BufferTime

[Joel-PeakMetrics]

Hello,

I'm looking to use Evt with my production codebase. The limited number of available operators could be a blocker for adoption. Could you please help me understand how hard it would be to add some of the available RxJS operators?

Here is one I'd like to have:
https://www.learnrxjs.io/learn-rxjs/operators/transformation/buffertime

If it is fairly easy to implement these operators using Evt, maybe we can continue our plan to use Evt in production.

TYIA!

[garronej]

Hello @Joel-PeakMetrics,

Thank you for getting in touch.

Regrettably, in the current iteration of EVT, operators do not have the capability to trigger a post-event. To provide a clear picture, EVT operators are primarily designed to accomplish three tasks:

• Modify or transform event data.
• Opt to not forward an event, often referred to as "swallowing" an event.
• Maintain an internal state.

In relation to bufferTime, it's feasible to craft an operator that amasses events into an array. However, the system limitation lies in that we cannot predetermine that the buffer should be purged every X milliseconds.
We can only establish that upon receiving a new event, the buffer should be cleared if more than X milliseconds have elapsed. This, admittedly, diverges from our desired outcome.

However, this limitation doesn't signify that EVT cannot accommodate such scenarios. I have put together a bufferTime implementation using a standard function in this playground: EVT Playground

Moreover, it's worth noting that we have charted plans for the upcoming EVT v3 which includes the functionality of enabling operators to delay posts. For more details, you may refer to the EVT v3 roadmap.

I hope that this option constitute a satisfactory solution to your query. Please don't hesitate to reach out if you require any further clarification or insights.

Best Regards

[Joel-PeakMetrics]

Thank you for your response! Do you have a time frame in mind for the release of Evt v3?

…

On Sun, Jul 2, 2023, 2:41 PM Joseph Garrone ***@***.***> wrote: Hello @Joel-PeakMetrics <https://github.com/Joel-PeakMetrics>, Thank you for getting in touch. Regrettably, in the current iteration of EVT, operators do not have the capability to trigger a post-event. To provide a clear picture, EVT operators are primarily designed to accomplish three tasks: Modify or transform event data. Opt to not forward an event, often referred to as "swallowing" an event. Maintain an internal state. In relation to bufferTime, it's feasible to craft an operator that amasses events into an array. However, the system limitation lies in that we cannot predetermine that the buffer should be purged every X milliseconds. We can only establish that upon receiving a new event, the buffer should be cleared if more than X milliseconds have elapsed. This, admittedly, diverges from our desired outcome. However, this limitation doesn't signify that EVT cannot accommodate such scenarios. I have put together a bufferTime implementation using a standard function in this playground: EVT Playground <https://stackblitz.com/edit/evt-playground-qh6jhy?file=index.ts> Moreover, it's worth noting that we have charted plans for the upcoming EVT v3 which includes the functionality of enabling operators to delay posts. For more details, you may refer to the EVT v3 roadmap <#63>. I hope that this option constitute a satisfactory solution to your query. Please don't hesitate to reach out if you require any further clarification or insights. Best Regards — Reply to this email directly, view it on GitHub <#62 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A6BNNYSHMMZOTDRKYX737ATXOHMJPANCNFSM6AAAAAAZ3TPIB4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[garronej]

Unfortunately I have no precise timeline.

I would like to introduce ts-pattern into EVT, I feel it has the potential of greatly improving the developper experience.

However I can't proceede until this PR gets merged.
I won't introduce a dependency that isn't published on deno.land/x.

Best,