[lib] Allow overriding a keyserver in a function returned from useKeyserverCall hook
AbandonedPublic
Actions

Authored by tomek on Dec 12 2023, 4:12 AM.

Details

Reviewers

michal
rohan
inka
bartek

Summary

Modifying the keyserver by setting a parameter of a hook appeared to be really complicated when we don't know the keyserver when rendering a component. This diff allows overriding when calling a function.

Depends on D10308

Test Plan

Check if calling link verification works with default and overridden keyserver.

Diff Detail

Repository

rCOMM Comm

Branch

linki

Lint

No Lint Coverage

Unit

No Test Coverage

Event Timeline

tomek created this revision.Dec 12 2023, 4:12 AM

Herald added a subscriber: ashoat. · View Herald TranscriptDec 12 2023, 4:12 AM

Harbormaster completed remote builds in B24990: Diff 34530.Dec 12 2023, 5:04 AM

tomek requested review of this revision.Dec 12 2023, 5:04 AM

Use optional

Harbormaster completed remote builds in B24991: Diff 34531.Dec 12 2023, 5:51 AM

tomek planned changes to this revision.Dec 12 2023, 6:15 AM

tomek added inline comments.

lib/utils/keyserver-call.js
103–106 ↗	(On Diff #34530)	There's an issue with memoization here, when we provide a next argument - this requires changing the solution

Probably fix the override. This still requires a lot of testing and thinking about
memoization, but it isn't broken in an obvious way.

Harbormaster completed remote builds in B25019: Diff 34565.Dec 13 2023, 6:51 AM

tomek added a child revision: D10338: [web][native] Download invite link blob and use it as an override.Dec 14 2023, 6:52 AM

Makes sense to me but I might not have enough context to be sure

This diff still has an issue: when calling a new keyserver, it returns sessionChange which causes setNewSession to be dispatched - this results in the keyserver being added to a store in an incorrect way and breaks more things down the line.

In D10311#299753, @tomek wrote:

This diff still has an issue: when calling a new keyserver, it returns sessionChange which causes setNewSession to be dispatched - this results in the keyserver being added to a store in an incorrect way and breaks more things down the line.

I'm seeing the same thing with the getVersion call in the new registration flow. Created ENG-6097 to track.