[FIX] Remove Livechat guest data was removing more rooms than expected#14509
Merged
[FIX] Remove Livechat guest data was removing more rooms than expected#14509
Conversation
rodrigok
changed the title
rodrigok
approved these changes
May 15, 2019
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #14506.
There was an issue when removing Livechat guest data. The method to find the guest wasn't returning an object, so the
tokenproperty was gettingnull.The big problem was that by passing
nulltoRooms.findByVisitorTokenmethod, all rooms were returned instead of return nothing.Other enhancements have also been added, such as adding
visitordata tosubscriptions. This data was missing while removing subscriptions related to the visitor.