Page MenuHomePhabricator

[native] Merge registration and sign in navigators
ClosedPublic

Authored by tomek on Jan 10 2025, 10:10 AM.
Tags
None
Referenced Files
Unknown Object (File)
Sun, Mar 9, 8:57 PM
Unknown Object (File)
Sun, Mar 9, 8:57 PM
Unknown Object (File)
Sun, Mar 9, 8:57 PM
Unknown Object (File)
Sun, Mar 9, 8:57 PM
Unknown Object (File)
Feb 18 2025, 8:35 AM
Unknown Object (File)
Feb 18 2025, 8:35 AM
Unknown Object (File)
Feb 3 2025, 3:29 PM
Unknown Object (File)
Feb 3 2025, 3:29 PM
Subscribers

Details

Summary

As a part of the registration flow we might need to open a screen from the restoration navigator and continue with the restoration flow. To make this interaction better, we need to have both flows in the same navigation structure.

https://linear.app/comm/issue/ENG-10040/handle-existing-wallet-registration

Depends on D14186

Test Plan

Check if it is possible to open both registration and restoration screens.

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

native/account/logged-out-modal.react.js
402–406 ↗(On Diff #46641)

For some reason, Flow complains when navigation from the props is used (it tells that screen property isn't present). We're using useNavigation in some other places, so the simplest solution was to use this approach.

native/account/registration/registration-navigator.react.js
152 ↗(On Diff #46641)

All the related entities are renamed in the next diff because they are no longer registration-specific.

Harbormaster returned this revision to the author for changes because remote builds failed.Jan 10 2025, 10:24 AM
Harbormaster failed remote builds in B33219: Diff 46641!
kamil added inline comments.
native/account/restore-password-account-screen.react.js
18 ↗(On Diff #46645)

nit

This revision is now accepted and ready to land.Jan 13 2025, 2:39 AM