-
Notifications
You must be signed in to change notification settings - Fork 13k
chore: remove useReactiveValue from useReplyInDMAction
#36217
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
Conversation
|
Looks like this PR is ready to merge! 🎉 |
|
useReactiveVar from useReplyInDMActionuseReactiveValue from useReplyInDMAction
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #36217 +/- ##
========================================
Coverage 64.53% 64.54%
========================================
Files 3148 3148
Lines 104625 104632 +7
Branches 19774 19777 +3
========================================
+ Hits 67522 67535 +13
+ Misses 34413 34408 -5
+ Partials 2690 2689 -1
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
e1bd4f6 to
cc28d59
Compare
…ocketChat#36217)" This reverts commit 1d6f335. Reverting experimentally to see if this commit changed the behavior of "Reply in direct message" (hiding it when there is no pre-existing room)
…e-d permission When PR RocketChat#36217 refactored useReplyInDMAction, it introduced a regression. We previously checked for `!canCreateDM` (with a bang!) but that PR accidentally negated it to `canCreateDM`. Additionally, the conditional that includes `canCreateDM` was duplicated. DRY it out.
…e-d permission When PR RocketChat#36217 refactored useReplyInDMAction, it introduced a regression. We previously checked for `!canCreateDM` (with a bang!) but that PR accidentally negated it to `canCreateDM`. Additionally, the conditional that includes `canCreateDM` was duplicated. DRY it out.
ARCH-1651
Proposed changes (including videos or screenshots)
Replace
useReactiveValuein favor of ZustandIssue(s)
Steps to test or reproduce
Further comments