This repository has been archived by the owner on Nov 21, 2020. It is now read-only.
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.
We have implemented an user assigned chat isolation option to follow this behavior:
1 - New chat appears for every one in the channel(no assigned user)
2 - An user assumes the chat, meaning he is assigned to that chat
3 - Chat with the new designated user "disappears" from other users
4 - If need, the user previous assigned or the admin, can assign other user to continue the chat(like a transfer)
We also made a change (in the option "USE_BRAND_RESTRICTIONS") on user selection by brand because the behavior wasn't loading the users correctly in this situations:
Expected behavior: If user has no brand, it should load all brands
To use this behavior, you should set the ENV property "USE_CHAT_RESTRICTIONS" to "true"
.env file:
USE_CHAT_RESTRICTIONS=true