-
Notifications
You must be signed in to change notification settings - Fork 281
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
fix: make channel.visible
respect archived and pinned channels
#2633
Conversation
119d82f
to
3219f4a
Compare
3219f4a
to
b7b5ce2
Compare
Size Change: 0 B Total Size: 1.2 MB ℹ️ View Unchanged
|
28d4fbf
to
2a56266
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2633 +/- ##
==========================================
- Coverage 80.78% 80.76% -0.03%
==========================================
Files 450 450
Lines 9646 9650 +4
Branches 2301 2302 +1
==========================================
+ Hits 7793 7794 +1
- Misses 1733 1736 +3
Partials 120 120 ☔ View full report in Codecov by Sentry. |
2a56266
to
1c7639a
Compare
type: event.channel.type, | ||
}); | ||
|
||
const considerArchivedChannels = shouldConsiderArchivedChannels(filters); |
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.
Ah, I think I missed this bit - I could it could happen that a channel
is archived and hidden so making it visible should respect the archive first, right ?
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 mean - realistically this should never happen but it's there to respect the filter value in case it ever happens (whatever the actual integration looks like). I just copied and slightly adjusted the notification.message_new
handler.
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 no, it's totally on point - I just missed it when doing the fixes 👍
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.
Looks good ! Don't forget to remove this if you intended to do so (or this can happen once we merge the LLC PR too)
1c7639a
to
cc4a24d
Compare
cc4a24d
to
ab98d77
Compare
## [12.11.0](v12.10.0...v12.11.0) (2025-02-07) ### Bug Fixes * change useStateStore to use useSyncExternalStore ([#2573](#2573)) ([6f2de4e](6f2de4e)) * make `channel.visible` respect archived and pinned channels ([#2633](#2633)) ([2d2e2e5](2d2e2e5)) ### Features * allow custom ReactionsListModal ([#2632](#2632)) ([a428dc9](a428dc9)) * allow to search for channels only ([#2625](#2625)) ([a4d6d83](a4d6d83)) ### Chores * **deps:** upgrade @stream-io/stream-chat-css to version 5.7.0 ([#2636](#2636)) ([8b7cfba](8b7cfba))
🎉 This PR is included in version 12.11.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎯 Goal
References: GetStream/stream-chat-react-native#2925