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

Remove unused retry parameter from safelyExecute #787

Merged
merged 2 commits into from
Apr 20, 2022

Conversation

Gudahtt
Copy link
Member

@Gudahtt Gudahtt commented Apr 20, 2022

The retry parameter of safelyExecute was unused, so it has been removed. Generally this parameter does not seem useful, and we are trying to remove all uses of this function anyway.

This makes updating to TypeScript v4.4 slightly easier, because the invocation of the retry function is a type error on that version (because error is unknown).

The `retry` parameter of `safelyExecute` was unused, so it has been
removed. Generally this parameter does not seem useful, and we are
trying to remove all uses of this function anyway.

This makes updating to TypeScript v4.4 slightly easier, because the
invocation of the retry function is a type error on that version
(because `error` is `unknown`).
@Gudahtt Gudahtt requested a review from a team as a code owner April 20, 2022 15:23
@Gudahtt Gudahtt merged commit 7256c7e into main Apr 20, 2022
@Gudahtt Gudahtt deleted the remove-safely-execute-retry branch April 20, 2022 15:42
MajorLift pushed a commit that referenced this pull request Oct 11, 2023
The `retry` parameter of `safelyExecute` was unused, so it has been
removed. Generally this parameter does not seem useful, and we are
trying to remove all uses of this function anyway.

This makes updating to TypeScript v4.4 slightly easier, because the
invocation of the retry function is a type error on that version
(because `error` is `unknown`).
MajorLift pushed a commit that referenced this pull request Oct 11, 2023
The `retry` parameter of `safelyExecute` was unused, so it has been
removed. Generally this parameter does not seem useful, and we are
trying to remove all uses of this function anyway.

This makes updating to TypeScript v4.4 slightly easier, because the
invocation of the retry function is a type error on that version
(because `error` is `unknown`).
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

Successfully merging this pull request may close these issues.

2 participants