Page MenuHomePhabricator

[native] Rename get/setCurrentUserID in CommCoreModule
ClosedPublic

Authored by ashoat on Apr 16 2024, 4:58 AM.
Tags
None
Referenced Files
Unknown Object (File)
Sun, Nov 3, 10:36 AM
Unknown Object (File)
Oct 13 2024, 1:10 AM
Unknown Object (File)
Oct 13 2024, 1:10 AM
Unknown Object (File)
Oct 13 2024, 1:10 AM
Unknown Object (File)
Oct 13 2024, 1:09 AM
Unknown Object (File)
Oct 13 2024, 1:09 AM
Unknown Object (File)
Oct 5 2024, 3:01 AM
Unknown Object (File)
Aug 29 2024, 8:12 PM
Subscribers

Details

Summary

While working on ENG-7667, I spent some time reviewing this logic in SQLiteDataHandler on native. I found that the use of these methods might be more clear with a better name.

My mental model for it is:

  1. A SQLite database is "stamped" once a user logs in
  2. If a SQLite database is "stamped" with a given user ID, then it will deleted as soon as that user is not the current user
Test Plan
  1. Flow
  2. Compile the iOS app to a simulator and log in and log out. Make sure database is deleted

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Open to different names, but I want to avoid currentUserID, so that we're not making it seem like this is duplicate data

Harbormaster returned this revision to the author for changes because remote builds failed.Apr 16 2024, 5:11 AM
Harbormaster failed remote builds in B28237: Diff 39143!

I should probably also rename workerRequestMessageTypes.GET_CURRENT_USER_ID, workerRequestMessageTypes.SET_CURRENT_USER_ID, and any other related stuff

EDIT

Will do that in a separate diff... I think reviewers might be slightly different

EDIT 2

D11668

Should we regenerate a wasm file?

This revision is now accepted and ready to land.Apr 17 2024, 4:32 AM

Should we regenerate a wasm file?

It is not necessary. Methods modified by this diff are not exported to WASM since they don't appear in SQLiteQueryExecutorBindings.cpp.