-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Channel deletion #1444
Channel deletion #1444
Conversation
…to feature/delete-channel
…to feature/delete-channel
…message about channel deletion
…st for ownerNickname
* Make channel tiles swipeable * Add DeleteChannel component * Add channel deletion screen * Attach channel deletion action * Fix mobile typings and tests * Remove call for clearing invitation code * Lint * Use state-managers delete action * Restore invitaion code handling in sm * Fix saga test for handling invitation code * Fix RTL tests
…ze e2e tests, fix mention in message
packages/state-manager/src/sagas/publicChannels/deletedChannel/deletedChannel.saga.test.ts
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It may be minor but I wish this saga was divided into two separate sagas: one for clearing up the store and second for sending owner's notification to general channel. It's all about limiting the responsibility of a single saga.
Also 'deletedChannel' might not be the right name... I'm thinking about something like 'channelDeletionResponseSaga' - to make it obvious that this should trigger after the channel has been deleted by backend
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will do that in next PR
No description provided.