in our identity login actions, we should check the exception message and if it tells us that the username/wallet address is reserved, we should attempt reserved registration (if possible, i.e. if on native)
Depends on D11911
Details
Details
called the useLogIn hooks with a reserved username and reserved wallet address and confirming that i was registered on identity. this will be tested further in next diff which will use the login hook from the native handler component responsible for background authing users who are missing a CSAT
Diff Detail
Diff Detail
- Repository
- rCOMM Comm
- Branch
- delete-user-client (branched from master)
- Lint
No Lint Coverage - Unit
No Test Coverage
Event Timeline
| lib/actions/user-actions.js | ||
|---|---|---|
| 661–673 | not sure why, but flow wasn't able to see that identityClient.registerReservedPasswordUser is not undefined inside this condition, so i used the registerReservedPasswordUser function, which calls identityClient.registerReservedPasswordUser. would like to avoid this indirection if there's a better way to resolve the flow issue | |
| lib/actions/user-actions.js | ||
|---|---|---|
| 661–673 | I think you can avoid it if you extract registerReservedPasswordUser to a local varible before checking it | |