v1.6.1

What's Changed

• Fix documentation for Scope value resolving by type by @kuyugama in #66

Full Changelog: v1.6.0...v1.6.1

V1.6.0 | Scope as a class

New Feature: Scope object and Type Factories

This release introduces the new Scope class, which is intended as a more structured and powerful replacement for the plain, dictionary-based scopes used previously.

Scope Class

The Scope object provides a formal structure for defining dependencies, including named values, typed instances, and the new type factories.

To ensure backward compatibility, your existing code will continue to work as expected. Legacy dictionary-based scopes are automatically converted into Scope objects using the Scope.from_legacy method, so no changes are required for your existing implementations.

New Feature: Type Factories

This change also adds a completely new feature to fundi: Type Factories.

Type factories allow you to define a factory for a specific type, which will be executed on-demand whenever an instance of that type is required by a dependency.

Here is an example:

from fundi import Scope, inject

class UserService:
    def get_user(self, user_id: int) -> str:
        # In a real app, this would query a database
        return f"User_{user_id}"

# This factory will be called anytime a `UserService` is needed
def create_user_service() -> UserService:
    return UserService()

# Create a scope and add the factory
scope = Scope()
scope.add_factory(create_user_service)

# A dependant that needs `UserService`
def get_username(user_id: int, service: UserService) -> str:
    return service.get_user(user_id)

# `create_user_service` is called automatically inside `inject`
username = inject(scope, get_username, {"user_id": 1})
assert username == "User_1"

Important Note: Type factories provide an implicit way to define dependencies. While powerful, they should be used judiciously. For core application components and clearer dependency graphs, explicitly defining dependencies is often preferred.

What's Changed

• Configure ty and ruff for the project by @kuyugama in #63
• Improve from_(...) overloads for generators by @kuyugama in #64
• Injection scope as a class by @kuyugama in #65

Full Changelog: v1.5.0...v1.6.0

v1.5.0 | GPL -> LGPL license

What's Changed

• Change license to LGPL V3 by @kuyugama in #59

Full Changelog: v1.4.1...v1.5.0

v1.4.1

What's Changed

• Fix side-effect binding scope collision at first callable scan by @kuyugama in #58

Full Changelog: v1.4.0...v1.4.1

v1.4.0 | Python 3.14, side effects and scope hook

What's Changed

• Add python 3.14 support by @kuyugama in #52
• Add scope hook by @kuyugama in #53
• Add CITATION.cff by @kuyugama in #55
• Implement side effects by @kuyugama in #54
• Rewrite docs by @kuyugama in #56
• Add logging by @kuyugama in #57

Full Changelog: v1.3.7...v1.4.0

v1.3.7

Full Changelog: v1.3.6...v1.3.7

v1.3.5 | Optional Exit Stack

What's Changed

• Make stack parameter optional in [a]inject() function by @kuyugama in #51

Full Changelog: v1.3.4...v1.3.5

v1.3.4 | Graph hook

What's Changed

• Disable caching of the parameter-aware dependencies by default by @kuyugama in #48
• Revert "Disable caching of the parameter-aware dependencies by default" by @kuyugama in #50
• Add hook that is called when dependency is defined in dependant by @kuyugama in #49

Full Changelog: v1.3.3...v1.3.4

v1.3.3 | Dependencies inside typing.Annotated

What's Changed

• Add support of defining dependencies using typing.Annotated by @kuyugama in #47

Full Changelog: v1.3.2...v1.3.3

v1.3.2

What's Changed

• If normalize_annotation returned non-type value use its type by @kuyugama in #46

Full Changelog: v1.3.1...v1.3.2