486 list doesnt get populated immediately when successfully submitting share permissions #488
Conversation
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
…o refresh the list of roles in state
longshuicy
reviewed
May 4, 2023
| const users = useSelector((state: RootState) => state.group.users); | ||
|
|
||
| const setUserRole = (datasetId: string, username: string, role: string) => | ||
| const setUserRole = async (datasetId: string, username: string, role: string) => |
Contributor
Author
There was a problem hiding this comment.
To make sure that when the subsequent listRoles is called, the update is already reflected in the backend
Member
There was a problem hiding this comment.
ah sorry i didn't realize you are directly using dispatch :-) My bad it makes perfect sense now.
max-zilla
approved these changes
May 4, 2023
max-zilla
deleted the
486-list-doesnt-get-populated-immediately-when-successfully-submitting-share-permissions
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Screen.Recording.2023-05-03.at.8.34.47.PM.mov