Feature: Add resource type parameter to init and shutdown resources using specialized providers

[amoncusir]

Objective

Enable the initialization and shutdown of resources by specifying their type. This allows you to create logical groups of resources and handle them by type, similar to applying resource scoping.

Changes

• New Argument: Added an optional argument to both Container.init_resources and Container.shutdown_resources to specify which resource type(s) should be processed.
• Tests: Added tests to ensure that resource scoping works correctly, including scenarios where dependent resources belong to different types.
• Docs: Added documentation on resource to explain how can be used

[colo-o]

Pretty useful!

[wadinj]

@ZipFile any changes to make this merge?

[ZipFile]

Hey! Sorry for delay. I have mixed feeling about this change, since this is not a proper scoping implementation, but rather a workaround. Either way, I think we can accept it for now, since introducing real scopes would probably require some serious re-engeneering on our part.

I've left some comments to the code + we need to add support for passing provider class in the Lifespan from dependency_injector.ext.starlette.

[amoncusir]

Hey! Sorry for delay. I have mixed feeling about this change, since this is not a proper scoping implementation, but rather a workaround. Either way, I think we can accept it for now, since introducing real scopes would probably require some serious re-engeneering on our part.

I've left some comments to the code + we need to add support for passing provider class in the Lifespan from dependency_injector.ext.starlette.

Yep! Exactly, it's a workaround. When I started with this, my first approach was to refact the current Resource class, but as you said, requieres a serious re-engeneering and this small change just do the work and provide a way to init indpendenent resources.

[coveralls]

coverage: 94.59% (+0.006%) from 94.584%
when pulling 4604341 on amoncusir:feat/specifit_resource_type
into b411807 on ets-labs:develop.

[cursor-com]

Bug: Invalid Resource Type Causes Incorrect Error

The init_resources and shutdown_resources methods raise a generic TypeError ("issubclass() arg 1 must be a class") when the resource_type parameter is a non-class value (e.g., None, string, number). This occurs because the issubclass() check is performed directly on the input without first validating if resource_type is a class, leading to inconsistent error messages compared to the intended custom TypeError.

src/dependency_injector/containers.pyx#L320-L322

python-dependency-injector/src/dependency_injector/containers.pyx

Lines 320 to 322 in 4604341

	if not issubclass(resource_type, providers.Resource):
	raise TypeError("resource_type must be a subclass of Resource provider")

Fix in Cursor

---

Was this report helpful? Give feedback by reacting with 👍 or 👎