Page MenuHomePhabricator

[lib/native] Remain consistent with url naming pattern
ClosedPublic

Authored by rohan on Sep 8 2023, 7:52 AM.
Tags
None
Referenced Files
F3140878: D9112.diff
Sun, Nov 3, 5:34 AM
Unknown Object (File)
Sun, Oct 27, 8:44 AM
Unknown Object (File)
Fri, Oct 18, 6:26 PM
Unknown Object (File)
Mon, Oct 14, 3:06 AM
Unknown Object (File)
Mon, Oct 14, 3:06 AM
Unknown Object (File)
Mon, Oct 14, 3:06 AM
Unknown Object (File)
Mon, Oct 14, 3:06 AM
Unknown Object (File)
Mon, Oct 14, 2:59 AM
Subscribers

Details

Summary

Quick follow up for this comment. Though we no longer use parseKeysFromQRCodeURL, we have parseInstallReferrerFromInviteLinkURL. I decided to
match the convention with inviteLinkUrl and qrCodeLinkUrl, so I've renamed parseInstallReferrerFromInviteLinkURL to parseInstallReferrerFromInviteLinkUrl.

Test Plan

Ran flow and confirmed no errors

Diff Detail

Repository
rCOMM Comm
Branch
names
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

rohan requested review of this revision.Sep 8 2023, 8:10 AM
This revision is now accepted and ready to land.Sep 8 2023, 8:57 AM
ginsu requested changes to this revision.Sep 8 2023, 9:01 AM

actually after doing a quick global search it seems like the pattern is to have url be "URL" (it's not perfect throughout the codebase, but seems like the majority of cases go with all caps) . Could we make inviteLinkUrl => inviteLinkURL and qrCodeLinkUrl => qrCodeLinkURL

This revision now requires changes to proceed.Sep 8 2023, 9:01 AM

Rename all instances of '...Url' with '...URL'

This revision is now accepted and ready to land.Sep 8 2023, 5:47 PM