feat: add FullScopePolicy pass-through scoping policy - #578
Merged
feanil merged 1 commit intoSep 15, 2026
Merged
Conversation
feanil
approved these changes
Sep 15, 2026
The `scoping` module ships the ScopingPolicy interface and the
ScopedQuerysetMixin that applies it, but no concrete policy. A list
endpoint whose permission_classes already restrict callers to subjects
that may see every row (a platform-admin list, for example) still has to
supply a policy to use the mixin, so each such view ends up hand-writing
the same pass-through class (see openedx-platform#39037 review).
* FullScopePolicy — returns the queryset unchanged. Views that need no
narrowing set `scoping_policy = FullScopePolicy()` and stay wired for
record-visibility scoping, so a narrower policy can replace it later
without touching the view.
Bumps version to 10.9.0 and adds unit tests.
feanil
force-pushed
the
feat/full-scope-policy
branch
from
September 15, 2026 16:51
c1cec2c to
60f25d8
Compare
feanil
enabled auto-merge (rebase)
September 15, 2026 16:51
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
2 participants
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.
Add
FullScopePolicyto thescopingmodule.The module ships the
ScopingPolicyinterface and theScopedQuerysetMixinthat applies it, but no concrete policy. A list endpoint whosepermission_classesalready restrict callers to subjects that may see every row (a platform-admin list, for example) still has to supply a policy to use the mixin, so each such view ends up hand-writing the same pass-through class. This came up in review of openedx/openedx-platform#39037, where the suggestion was a shared "FullScopePolicy" usable in many places; since it is reusable DRF tooling, it belongs here next to the mixin so plugins can use it too.FullScopePolicy— returns the queryset unchanged. Views that need no narrowing setscoping_policy = FullScopePolicy()and stay wired for record-visibility scoping, so a narrower policy can replace it later without touching the view.Bumps version to 10.9.0 and adds unit tests.