-
Notifications
You must be signed in to change notification settings - Fork 277
Jon/fix/same addr swap #5706
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
Jon/fix/same addr swap #5706
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some small things, plus of course the core issue.
| /> | ||
| )) | ||
| return | ||
| } catch (e) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doesn't ESLint require this to be (e: unknown)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please fix still?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't get any linter warnings here...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@typescript-eslint/use-unknown-in-catch-callback-variable, applies to Promise .catch(...) callback parameters, not try { ... } catch (e) { ... }. It will not flag a try/catch clause.
The TypeScript option useUnknownInCatchVariables: true (true by default) only changes the inferred type of the catch variable to unknown. It does not require an explicit : unknown annotation and does not warn at the catch site. Errors will appear only where you use e unsafely (for example, e.message without narrowing), not at catch (e).
605ea20 to
54e173a
Compare
swansontec
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like not all the comments from the first review got addressed.
| /> | ||
| )) | ||
| return | ||
| } catch (e) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please fix still?
3e5239e to
b4db080
Compare
b4db080 to
b181189
Compare
CHANGELOG
Does this branch warrant an entry to the CHANGELOG?
Dependencies
noneRequirements
If you have made any visual changes to the GUI. Make sure you have: