chore: pass explicit validate= to root Container() in tests#3
Merged
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds an explicit
validate=Trueargument to the three bare rootmodern_di.Container(...)constructions in this repo's tests (tests/conftest.py,tests/test_lifespan.pyx2).README.mdalready passedvalidate=Trueexplicitly, so no change was needed there.Why
The next modern-di 2.x minor introduces
UnvalidatedContainerWarning(aFutureWarning) when a root container is built without an explicitvalidateargument. 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 passedjust test-ci— 10 passed, 100% coveragejust lint-ci— eof-fixer, ruff format, ruff check, ty, planning index all clean🤖 Generated with Claude Code