Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RetryConfig documentation link broken #7030

Closed
kihuha opened this issue Jul 28, 2022 · 3 comments
Closed

RetryConfig documentation link broken #7030

kihuha opened this issue Jul 28, 2022 · 3 comments

Comments

@kihuha
Copy link

kihuha commented Jul 28, 2022

Describe the bug

While reading the documentation on the "retry" operator, I wanted more information on how to configure it using the "RetryConfig". On clicking the RetryConfig link shown in the screenshot below, the page was not found at https://rxjs.dev/api/operators/retry.

Screenshot 2022-07-28 at 11 43 07

Expected behavior

The RetryConfig page should be available

Reproduction code

- Navigate to https://rxjs.dev/api/operators/retry
- Scroll to the section describing how to use the RetryConfig object
- Click on the "RetryConfig" link


Alternatively:
- Navigate to https://rxjs.dev/RetryConfig

Reproduction URL

No response

Version

7

Environment

No response

Additional context

No response

@bdirito
Copy link

bdirito commented Aug 8, 2022

Note that RetryWhen documents also reference what I assume is this RetryConfig item

[RetryWhen] Will be removed in v9 or v10, use [retry](https://rxjs.dev/api/operators/retry)'s [delay](https://rxjs.dev/api/index/function/delay) option instead.

@BobbyCGD
Copy link

Still broken, alternative is to go straight to the code instead =>

https://github.com/ReactiveX/rxjs/blob/master/src/internal/operators/retry.ts

@jakovljevic-mladen
Copy link
Member

This is fixed in #6943 and it's now published to the official docs. Thanks for reporting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants