Skip to content

chore: pass explicit validate= to root Container() in tests#3

Merged
lesnik512 merged 1 commit into
mainfrom
chore/explicit-validate
Jul 6, 2026
Merged

chore: pass explicit validate= to root Container() in tests#3
lesnik512 merged 1 commit into
mainfrom
chore/explicit-validate

Conversation

@lesnik512

Copy link
Copy Markdown
Member

What

Adds an explicit validate=True argument to the three bare root modern_di.Container(...) constructions in this repo's tests (tests/conftest.py, tests/test_lifespan.py x2). README.md already passed validate=True explicitly, so no change was needed there.

Why

The next modern-di 2.x minor introduces UnvalidatedContainerWarning (a FutureWarning) when a root container is built without an explicit validate argument. Passing it explicitly future-proofs the suite against warning noise and dogfoods graph validation. No assertion on the warning itself was added, since the currently pinned modern-di release doesn't emit it yet.

Test plan

  • just test — 10 passed
  • just test-ci — 10 passed, 100% coverage
  • just lint-ci — eof-fixer, ruff format, ruff check, ty, planning index all clean

🤖 Generated with Claude Code

The next modern-di 2.x minor introduces UnvalidatedContainerWarning
when a root container is built without an explicit validate argument.
Passing validate=True future-proofs the suite against that warning
noise and dogfoods graph validation.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@lesnik512 lesnik512 merged commit d6cd6a6 into main Jul 6, 2026
6 checks passed
@lesnik512 lesnik512 deleted the chore/explicit-validate branch July 6, 2026 08:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant