Page MenuHomePhabricator

[native] introduce UserProfileAvatarModal
ClosedPublic

Authored by ginsu on Oct 5 2023, 12:24 PM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Dec 18, 9:26 PM
Unknown Object (File)
Wed, Dec 18, 9:26 PM
Unknown Object (File)
Wed, Dec 18, 9:26 PM
Unknown Object (File)
Wed, Dec 18, 9:25 PM
Unknown Object (File)
Wed, Dec 18, 9:22 PM
Unknown Object (File)
Fri, Nov 29, 1:17 PM
Unknown Object (File)
Mon, Nov 25, 6:09 PM
Unknown Object (File)
Mon, Nov 25, 3:09 AM
Subscribers

Details

Summary

This diff introduces the User Profile Avatar Modal component. The User Profile Avatar Modal uses the new FullScreenViewModal and XXL avatar size that I introduced earlier.

This is step 4 in the list below
Outlined below are the steps I will take in this stack (each point here will be it's own diff):

  1. Replace out of box BottomSheetModal with basic BottomSheet (Unfortunately, BottomSheetModal does not play nice with nested navigator)
  2. Polish up the BottomSheetBackdrop animation
  3. Introduce User Profile Bottom Sheet Navigators (this is so we can navigate to User Profile Avatar Modal from the User Profile Bottom Sheet)
  4. Introduce the User Profile Avatar Modal component and all the necessary things (like route names) that we will need to navigate to this new screen
  5. Factor out the User Avatar component in UserProfile into it's own separate component to keep things better organized

Depends on D9375

Test Plan

Confirmed that I was able to navigate to the User Profile Avatar Modal screen (the next diff will introduce the navigation method to this screen), and I can do things like zoom, pan, etc with the user avatars

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

ginsu edited the test plan for this revision. (Show Details)
ginsu added reviewers: atul, inka.
ginsu requested review of this revision.Oct 5 2023, 12:41 PM

Accepting to unblock, but would prefer if we could avoid passing contentDimensions to FullScreenViewModal

native/user-profile/user-profile-avatar-modal.react.js
42 ↗(On Diff #31694)

Eh, seems a little weird that we're passing the dimensions of the child to the parent FullScreenViewModal. What happens if the dimensions of XXL UserAvatar changes for example?

Is there a way to avoid this?

This revision is now accepted and ready to land.Oct 5 2023, 4:23 PM
native/user-profile/user-profile-avatar-modal.react.js
42 ↗(On Diff #31694)

would prefer if we could avoid passing contentDimensions to FullScreenViewModal

Since the logic for finding the dimensions of the user profile and an image multimedia message are pretty different from each other, I think it makes sense to still have a contentDimensions prop that can be used by FullScreenViewModal

https://github.com/CommE2E/comm/blob/master/native/media/image-modal.react.js#L63-L95

What happens if the dimensions of XXL UserAvatar changes for example?

I'll create an avatar-constants file and create an XXL size constant that can be used in both Avatar and here. So if the dimensions of XXL ever change, then both of these places will be affected

native/user-profile/user-profile-avatar-modal.react.js
42 ↗(On Diff #31694)
ginsu edited the test plan for this revision. (Show Details)

rebase before landing

This revision was landed with ongoing or failed builds.Oct 5 2023, 6:38 PM
This revision was automatically updated to reflect the committed changes.