fix: Multiple permission update toasts are spawned #13584
Merged
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.
What does the PR do
Closes #13369
This behaviour is encountered only when updating the permissions in the channel edit popup because the community description is updated in 2 steps: 1 - Update the channel; 2 - update the permissions.
Flow:
In this case the permissions updates are processed twice. Once when the permission update is called to the backend and the second time when the event for the new community description is received.
To fix this the permissions are not updated anymore when the backend rpc is called. The update happens only when the community description signal is received.
Affected areas
Community permissions
Screenshot of functionality (including design for comparison)
Screen.Recording.2024-02-15.at.23.18.50.mov
Cool Spaceship Picture