Skip to content

Conversation

@Jon-edge
Copy link
Collaborator

@Jon-edge Jon-edge commented Aug 19, 2025

image

CHANGELOG

Does this branch warrant an entry to the CHANGELOG?

  • Yes
  • No

Dependencies

none

Requirements

If you have made any visual changes to the GUI. Make sure you have:

  • Tested on iOS device
  • Tested on Android device
  • Tested on small-screen device (iPod Touch)
  • Tested on large-screen device (tablet)

Copy link
Contributor

@swansontec swansontec left a 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) {
Copy link
Contributor

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)?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please fix still?

Copy link
Collaborator Author

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...

Copy link
Collaborator Author

@Jon-edge Jon-edge Aug 22, 2025

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).

@Jon-edge Jon-edge force-pushed the jon/fix/same-addr-swap branch 2 times, most recently from 605ea20 to 54e173a Compare August 22, 2025 00:27
Copy link
Contributor

@swansontec swansontec left a 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) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please fix still?

@Jon-edge Jon-edge force-pushed the jon/fix/same-addr-swap branch 4 times, most recently from 3e5239e to b4db080 Compare August 22, 2025 23:24
@Jon-edge Jon-edge force-pushed the jon/fix/same-addr-swap branch from b4db080 to b181189 Compare August 25, 2025 21:30
@Jon-edge Jon-edge enabled auto-merge August 25, 2025 21:30
@Jon-edge Jon-edge merged commit 46e0ac0 into develop Aug 25, 2025
3 checks passed
@Jon-edge Jon-edge deleted the jon/fix/same-addr-swap branch August 25, 2025 21:45
Jon-edge added a commit that referenced this pull request Aug 26, 2025
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.

3 participants