Open chemicL opened 1 year ago
Hi @chemicL - i'm keen to explore this one - could you please assign to me? Thanks
hi @chemicL - i was looking at how the retry has been ported from addons to the core as an inspiration for the repeat. Looks like the port hasn't been exactly 1;1 in terms of functionality so I assume that will be the case for repeat as well. Do we need to preserve all the functionality that's currently offered by the addons repeat? Any guidance will be appreciated.
@OlegDokuka can you please respond when you find a moment? (I'm going to be away for a few days)
@Desislav-Petrov we don't literally have to port impl from reactor-addons but rather create a shared common for both retry and repeat operators. That means the logic implemented in Retry builder can go into something like "CommonRecurring" (or whatever name we endup) and then implement Repeat builder having that base mechanism as well as Retry.
Got you - thanks, will have a go
Similarly to the way
Retry
is implemented with accompanyingretryWhen(RetrySpec)
operator, theRepeat
functionality from reactor-addons project should be implemented in reactor-core and phased out from reactor-extras (module of reactor-addons). It can potentially reuse the primitives that already exist for the retry functionality.