Skip to content

chore: pass explicit validate= to root Container constructions#21

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

chore: pass explicit validate= to root Container constructions#21
lesnik512 merged 1 commit into
mainfrom
chore/explicit-validate

Conversation

@lesnik512

Copy link
Copy Markdown
Member

Summary

  • Add validate=True to the two bare root modern_di.Container(...) constructions in this repo: tests/conftest.py and README.md's usage example.
  • build_child_container sites are unaffected (only root constructions are in scope).

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 now future-proofs this suite and README against warning noise once that release lands, and dogfoods graph validation. Not asserting the warning here since the currently pinned modern-di release doesn't emit it yet.

Test plan

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

🤖 Generated with Claude Code

Future-proofs the suite and README against the upcoming UnvalidatedContainerWarning
(FutureWarning) that modern-di 2.x will emit when a root container is built
without an explicit validate argument, and dogfoods graph validation.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@lesnik512 lesnik512 merged commit e4c4948 into main Jul 6, 2026
6 checks passed
@lesnik512 lesnik512 deleted the chore/explicit-validate branch July 6, 2026 08:34
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