-
Notifications
You must be signed in to change notification settings - Fork 13.1k
[FIX] Adjusted livechat fallbacks to take null values into account #26909
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
Codecov Report
@@ Coverage Diff @@
## develop #26909 +/- ##
===========================================
+ Coverage 39.90% 40.98% +1.08%
===========================================
Files 826 801 -25
Lines 18373 17920 -453
Branches 2019 1960 -59
===========================================
+ Hits 7332 7345 +13
+ Misses 10742 10279 -463
+ Partials 299 296 -3
Flags with carried forward coverage won't be shown. Click here to find out more. |
tassoevan
left a comment
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.
Nullish coalescing (e.g. a ?? b) could be better, but || is fine as we're expecting objects. Just keep it in mind when dealing with falsy primitives.
904e7cc
…livechat-null-room
|
This pull request introduces 1 alert when merging 05dcba1 into ca43434 - view on LGTM.com new alerts:
|
…26909) * [FIX] Adjusted livechat fallbacks to take null values into account * [FIX] Adjusted to clear defaultAgent when department is changed * [FIX] Fixed default guest info not being displayed * [FIX] Adjusted widget default values logic * [FIX] Removing unnecessary check * [FIX] Changed default values logic again to account for changes via api Co-authored-by: Tasso Evangelista <tasso.evangelista@rocket.chat>
OC-209
This pull request fixes:
nullvalues and fallback to the correct default value instead of breaking the widget.defaultAgentnot being cleared from cache when a new department is set