Skip to content

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

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

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

Conversation

@lesnik512

Copy link
Copy Markdown
Member

What

Adds an explicit validate=True to the two bare root modern_di.Container(...) constructions in tests (tests/conftest.py, tests/test_lifespan.py). README.md already had validate=True at its root container example, so no change 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 this suite against warning noise ahead of that release 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-ci — 8 passed, 100% coverage
  • just lint-ci — all checks passed

🤖 Generated with Claude Code

Future-proofs the suite against modern-di's upcoming UnvalidatedContainerWarning
(FutureWarning) for root containers built without an explicit validate argument,
and dogfoods graph validation in our fixtures.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@lesnik512 lesnik512 merged commit 4c1f5f1 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