Page MenuHomePhabricator

[native] helper for pake registration on client side
ClosedPublic

Authored by varun on Aug 10 2022, 4:33 PM.
Tags
None
Referenced Files
F2180863: D4800.diff
Wed, Jul 3, 3:44 PM
Unknown Object (File)
Fri, Jun 14, 1:37 PM
Unknown Object (File)
Thu, Jun 13, 4:48 PM
Unknown Object (File)
Fri, Jun 7, 5:23 AM
Unknown Object (File)
Fri, Jun 7, 5:18 AM
Unknown Object (File)
May 27 2024, 2:21 AM
Unknown Object (File)
May 27 2024, 2:21 AM
Unknown Object (File)
May 27 2024, 2:17 AM

Details

Summary

This helper function takes the registration response from the server and completes the final step on the client side. It handles the error mapping and checking if the ClientRegistration object is present

Depends on D4799

Test Plan

Tested two diffs later in the stack

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

varun requested review of this revision.Aug 10 2022, 4:42 PM

This diff adds huge amount of imports and doesn't use most of them. Please make sure that the diff contains only the relevant ones.

This revision is now accepted and ready to land.Aug 11 2022, 4:16 AM
In D4800#138707, @tomek wrote:

This diff adds huge amount of imports and doesn't use most of them. Please make sure that the diff contains only the relevant ones.

All of these imports are used by the end of the stack

In D4800#138812, @varun wrote:
In D4800#138707, @tomek wrote:

This diff adds huge amount of imports and doesn't use most of them. Please make sure that the diff contains only the relevant ones.

All of these imports are used by the end of the stack

Yes, I've noticed it, but it isn't a good pattern. We need to make sure that every diff which requires new imports is the one that adds them. This makes it easier to review the code and makes diffs to stand on their own.

In D4800#138819, @tomek wrote:
In D4800#138812, @varun wrote:
In D4800#138707, @tomek wrote:

This diff adds huge amount of imports and doesn't use most of them. Please make sure that the diff contains only the relevant ones.

All of these imports are used by the end of the stack

Yes, I've noticed it, but it isn't a good pattern. We need to make sure that every diff which requires new imports is the one that adds them. This makes it easier to review the code and makes diffs to stand on their own.

Agreed. I'll avoid this pattern going forward