Page MenuHomePhabricator

[native] Stop navigating to Add Members from community creation
ClosedPublic

Authored by inka on Jun 3 2024, 8:01 AM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Dec 17, 2:25 PM
Unknown Object (File)
Thu, Dec 12, 1:10 PM
Unknown Object (File)
Tue, Nov 26, 4:29 PM
Unknown Object (File)
Nov 16 2024, 2:34 AM
Unknown Object (File)
Nov 10 2024, 11:56 PM
Unknown Object (File)
Nov 10 2024, 11:42 PM
Unknown Object (File)
Nov 10 2024, 9:32 PM
Unknown Object (File)
Nov 10 2024, 6:35 PM
Subscribers

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

native/community-creation/community-configuration.react.js
43 ↗(On Diff #40871)

We cannot remove props because of react navigation. We do the same in other components, for example AppsDirectory

107 ↗(On Diff #40871)

Before, we would navigate to CommunityCreationMembersRouteName, where upon pressing "Add" or "Cancel" (the only two buttons allowing us to leave the screen) navigateToThread would be called. We want to do this right away, since we don't want to allow adding users to community roots

inka requested review of this revision.Jun 3 2024, 8:18 AM
native/community-creation/community-configuration.react.js
30 ↗(On Diff #40871)

Is this route used anywhere else, or should it be deleted?

tomek added inline comments.
native/community-creation/community-configuration.react.js
106–107 ↗(On Diff #40871)

Is it possible that communityThreadInfo will still be null here? Should we navigate conditionally, only when the thread info is present?

This revision is now accepted and ready to land.Jun 4 2024, 1:09 AM
native/community-creation/community-configuration.react.js
30 ↗(On Diff #40871)

We can remove it
D12306

Check if thread info is present