Roadmap step 7: boundary check

Open
#14 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
django, python
Domain
backend

Research direction

Read ADR 0003 and the import-checker ADR; the latter must be accepted before this work starts. This step depends on step 6, and its plan and task list are not yet filled in. Once the scope is defined, implement neolith check in report-only mode first, then enforcement per app, with checks against the app boundary.

Written by the indexing model from the issue text.

Description

roadmap

Delivers neolith check enforcing the app boundary (ADR 0003), report-only first, then enforced per app.

Depends on: step 6; an ADR for the import checker must be Accepted first (K5).

Plan and task list per S4: filled in when the step starts.

Dominant language
Python
Stars
1
Forks
0
Avg merge
5h 30m
Merged PRs (30d)
85

Getting set up

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 stack314/django-neolith

All issues in stack314/django-neolith

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.