-
Notifications
You must be signed in to change notification settings - Fork 10.9k
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(livechat): make trigger use correct dep on agent.next #32692
Conversation
🦋 Changeset detectedLatest commit: a48a14b The changes in this PR will be included in the next version bump. This PR includes changesets to release 32 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 ready to merge! 🎉 |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #32692 +/- ##
===========================================
- Coverage 55.62% 55.55% -0.08%
===========================================
Files 2637 2637
Lines 57308 57308
Branches 11868 11868
===========================================
- Hits 31880 31839 -41
- Misses 22741 22779 +38
- Partials 2687 2690 +3
Flags with carried forward coverage won't be shown. Click here to find out more. |
CORE-526
Fixes an issue that caused the request for
agent.next
on the widget to call the wrong department when using thesetDepartment
api endpoint in conjunction with a Livechat Trigger