Use object permissions in Tagging frontend [FC-0036] - #25
Closed
pomegranited wants to merge 1 commit into
Closed
Conversation
to determine which actions/menu items to show the user of a given Taxonomy.
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
1 participant
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.
Description
Uses the "user permissions" added to the Tagging REST API by openedx/openedx-core#138 to decide what actions (e.g. import, export, edit, delete) to present to the current user when viewing Tagging-related content.
Supporting information
Part of openedx/modular-learning#160
This is a temporary PR on the base branch for openedx#675 ; will create a proper upstream master PR once that's merged.
Testing instructions
TBD
Deadline
None