-
Notifications
You must be signed in to change notification settings - Fork 12.9k
fix: Persist userId when updating a canned response
#37277
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
🦋 Changeset detectedLatest commit: 784c8e8 The changes in this PR will be included in the next version bump. This PR includes changesets to release 41 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Looks like this PR is not ready to merge, because of the following issues:
Please fix the issues and try again If you have any trouble, please check the PR guidelines |
WalkthroughA patch-level fix for private canned responses adds conditional userId inclusion when updating user-scoped entries. Changes include modifying the update payload in saveCannedResponse, adding a test to verify userId persistence, and documenting the fix in a changeset entry. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Suggested labels
Suggested reviewers
Poem
Pre-merge checks and finishing touches✅ Passed checks (5 passed)
✨ Finishing touches
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #37277 +/- ##
===========================================
- Coverage 67.61% 67.58% -0.03%
===========================================
Files 3338 3338
Lines 113721 113721
Branches 20662 20654 -8
===========================================
- Hits 76895 76864 -31
- Misses 34143 34173 +30
- Partials 2683 2684 +1
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
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.
Actionable comments posted: 2
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Disabled knowledge base sources:
- Jira integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (3)
.changeset/long-melons-float.md(1 hunks)apps/meteor/ee/app/canned-responses/server/methods/saveCannedResponse.ts(1 hunks)apps/meteor/tests/end-to-end/api/livechat/15-canned-responses.ts(2 hunks)
🧰 Additional context used
🧬 Code graph analysis (1)
apps/meteor/tests/end-to-end/api/livechat/15-canned-responses.ts (1)
apps/meteor/tests/data/api-data.ts (2)
request(10-10)credentials(39-42)
Proposed changes (including videos or screenshots)
When updating a canned response, we were not properly persisting
userIdwhen editing a canned response, due to which we were unsetting theuserIdfield. This was causing weird issues on client side when viewing the list of canned responses.Issue(s)
Steps to test or reproduce
useruserIdFurther comments
SUP-855
Summary by CodeRabbit