Refactor retryWithEscalation

[benjamincharity]

Current issues:

1. It's functionally implemented in a way that is different from other operations on a stream (cognitive load).
2. It requires duplicate items to be passed in every time it is used.

switchMap((action) => {
  return retryWithEscalation<ClaimMap>({
    tokenName: 'Linkedin',
    originalAction: action,
    httpSourceObservable: this.service.getRedirectUrl().pipe(
      take(1),
      map((response) => {
        return new RouterActions.Go({external: true, path: [response.callback_uri]});
      }),
    ),
    actions$: this.actions$,
  }).pipe(
    catchError(() => {
      return of(new FlashActions.CreateAction(linkedinDownFlashMessage));
    }),
  );
}),

Proposal

Rewrite as an injectable class:

switchMap((action) => {
  return this.service.getRedirectUrl().pipe(
      take(1),
      this.retryService.retryWithEscalation(action),
      map((response) => {
        return new RouterActions.Go({external: true, path: [response.callback_uri]});
      }),
    )
}),

retryWithEscalation kills stream and emits new action (this is the only way since all following operators need to consume what is emitted by retryWithEscalation).

The retry class will get the store and actions stream injected via it's constructor.