Skip to content

docs: remove dashes and stray contrasts from prose #52

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lesnik512 merged 1 commit into from
Oct 17, 2026
Merged

docs: remove dashes and stray contrasts from prose #52

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,11 +1,11 @@
# AGENTS.md

[`CONTEXT.md`](CONTEXT.md) opens with what this package is and owns the vocabulary — read it before
[`CONTEXT.md`](CONTEXT.md) opens with what this package is and owns the vocabulary. Read it before
naming a concept in code, in a test name, or in an issue title.

## Commands

`just` (task runner) and `uv` (package manager). The [`justfile`](justfile) is the source of truth —
`just` (task runner) and `uv` (package manager). The [`justfile`](justfile) is the source of truth:
`just --list`, or read it.

## Workflow
Expand Down
6 changes: 3 additions & 3 deletions CONTEXT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,17 +10,17 @@ A term is listed only when there is a synonym to reject, or a meaning subtle eno
docs must agree on it. General programming vocabulary does not belong here, however heavily this
package uses it.

The domain terms are `modern-di`'s — `Container`, `Provider`, `Group`, `Scope`, `Resolution`,
The domain terms are `modern-di`'s: `Container`, `Provider`, `Group`, `Scope`, `Resolution`,
`Override`. That project's `CONTEXT.md` is the authority for all of them; nothing here redefines
one. Celery's vocabulary is Celery's — task, worker, broker, beat, and the pool names mean what
one. Celery's vocabulary is Celery's: task, worker, broker, beat, and the pool names mean what
[its docs](https://docs.celeryq.dev) say they mean. The three below are this package's own.

**Root container**:
The `Scope.APP` `Container` handed to `setup_di` and registered for the Celery app, outside its
`conf`; the worker lifecycle signals open and close it unless `setup_di` gets `manage_lifespan=False`,
which leaves that to the user, and every per-task child descends from it.
`fetch_di_container` returns this one.
_Avoid_: APP container, APP-scope container — both have been used for it, and neither says the thing
_Avoid_: APP container, APP-scope container. Both have been used for it, and neither says the thing
that matters at a call site, which is that this is the container a per-task child is built *from*.

**Per-task child container**:
Expand Down
Loading