Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Permission system done right.

Open
#381 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
authorization

Research direction

No file, test, or entry point is named. Start by locating the context-contract, nested-story, permission-validation, and Delegate implementations. Done should mean that assigning a user in a wrapper story runs the permission validators from nested stories and fails early, including delegated Celery tasks.

Written by the indexing model from the issue text.

Description

blog

Permission is an ideal example of the context contract additional rules and composition.

We have a nested story with a more strict permission rule than the wrapper story.

user has its place in each context contract and we attach different permission validation to it in each contract.

When the user will be assigned in the wrapper story, we'll run all its permission validators from all nested stories. So we'll fail early.

Some nested stories will run in the Celery task because of the Delegate feature. We can fail that early.

Dominant language
HTML
Stars
10
Forks
5
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dry-python/dry-python.github.io

All issues in dry-python/dry-python.github.io

Similar issues

More Security issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.