enter_scope when using @inject.

[alexanderlazarev0]

No description provided.

[alexanderlazarev0]

To-do:

• Documentation
• Update migration guide.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Flag	Coverage Δ
unittests	100.00% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
tests/test_injection.py	100.00% <100.00%> (ø)
that_depends/injection.py	100.00% <100.00%> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Copilot]

Pull Request Overview

This PR introduces an "enter_scope" parameter to the dependency injection decorator, allowing the injected function to automatically enter the specified context. Key changes include updating the injection logic in injection.py, adjusting tests to cover new behavior for synchronous, asynchronous, and generator functions, and revising documentation to reflect the new usage.

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
that_depends/injection.py	Added the "enter_scope" parameter and corresponding error checks in the injection logic.
tests/test_injection.py	Updated and added new tests to verify the behavior of the "enter_scope" flag.
docs/migration/v3.md	Updated migration instructions to use "enter_scope=True" instead of the former container_context pattern.
docs/introduction/scopes.md	Revised documentation to clarify that the scope is not entered by default.