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

no-multiple-resolved wrongly reports reject in try/catch block #443

Closed
burtek opened this issue May 24, 2023 · 1 comment
Closed

no-multiple-resolved wrongly reports reject in try/catch block #443

burtek opened this issue May 24, 2023 · 1 comment
Labels

Comments

@burtek
Copy link

burtek commented May 24, 2023

From #382, which I think wasn't fully fixed

try {
    resolve(someThrowingFn())
} catch (error) {
    reject(error)
}

still errors for me. It doesn't error if I do this:

try {
    const data = someThrowingFn()
    resolve(data)
} catch (error) {
    reject(error)
}

But those two are identical and should behave same way?

@brettz9
Copy link
Member

brettz9 commented Jul 21, 2024

This issue has apparently already been resolved as I am not able to replicate. Closing though feel free to comment further as needed.

@brettz9 brettz9 closed this as completed Jul 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants