-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
MM 45015 - auto follow threads #7463
Conversation
Hello @tanmaythole, Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here. |
app/screens/channel_info/options/auto_follow_threads/auto_follow_threads.tsx
Outdated
Show resolved
Hide resolved
This PR has been automatically labelled "stale" because it hasn't had recent activity. |
@tanmaythole Are you still working on this? Could you address the comments? |
Yes, give me some time. I will commit changes as soon as possible. |
}: Props) => { | ||
const isDMorGM = isTypeDMorGM(type); | ||
|
||
return ( | ||
<> | ||
{type !== General.DM_CHANNEL && | ||
{isCRTEnabled && ( | ||
<AutoFollowThreads channelId={channelId}/> |
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.
does this also apply to DM's ?
|
||
const toggleFollow = preventDoubleTap(() => { | ||
const props: Partial<ChannelNotifyProps> = { | ||
channel_auto_follow_threads: followedStatus ? 'off' : 'on', |
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.
you should be using the constants declared in the constants/channel file
channel_auto_follow_threads: followedStatus ? 'off' : 'on', | ||
}; | ||
setAutoFollow(!autoFollow); | ||
updateChannelNotifyProps(serverUrl, channelId, props); |
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.
what happens if this fails? I know is the same with other options, just want to see what would be the consequence and if we should also thing about this for the other options as well.
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.
Okay need to add checks for this and other option as well
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 think you need to run i18n-extract
as is missing the en.json
file
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.
No extra comments from my side.
This PR has been automatically labelled "stale" because it hasn't had recent activity. |
Building app in separate branch. |
Building app in separate branch. |
/update-branch |
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.
Thanks @tanmaythole
I'm going to qa-defer
this PR as I'm having trouble accessing master.test.mattermost.com
from mobile. I will test post merge.
cc// @johndavidlugtu @enahum
* auto follow select option added * unused code removed * auto follow threads condition fixed on CRT enabled * error handles --------- Co-authored-by: Mattermost Build <[email protected]>
* auto follow select option added * unused code removed * auto follow threads condition fixed on CRT enabled * error handles --------- Co-authored-by: Mattermost Build <[email protected]>
Summary
Added auto follow thread select option
Ticket Link
Fixes mattermost/mattermost#22386
https://mattermost.atlassian.net/browse/MM-45015
Checklist
Device Information
This PR was tested on: Samsung M11 - 12 version
Screenshots
Release Note