🐛♻️ Use AccessRights field instead of owner's email #3719
Merged
Conversation
This file contains 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
odeimaiz
added
a:frontend
odeimaiz
changed the title
odeimaiz
requested review from
pcrespov,
elisabettai,
GitHK,
mguidon,
mrnicegyu11 and
sanderegg
odeimaiz
changed the title
mguidon
approved these changes
Dec 20, 2022
…mcore into feature/less-is-owner
|
Kudos, SonarCloud Quality Gate passed!
|
sanderegg
approved these changes
Dec 20, 2022
6 tasks
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.
What do these changes do?
Study/Template/Service owner's email was widely used to check if a user had or not write/delete permissions on the resource. This PR gets rid of it and it checks the
accessRightsfield instead.Related issue/s
How to test
Checklist