Skip to content

Define Application Execution Boundary in DI #374

Closed

Description

@armanist

Scope

  • Make Di::reset() the official application execution boundary
  • Ensure it is called exactly once per App execution
  • No behavioral changes yet

Tasks

  • Document Di::reset() as the execution boundary
  • Call Di::reset() in AppFactory::create()
  • Ensure no mid-execution resets exist

Acceptance Criteria

  • One DI container per App execution
  • No static instances survive between runs

Activity

  1. added this to the 3.0.0 milestone on Dec 28, 2025
  2. self-assigned this
    on Apr 7, 2026
  3. added a commit that references this issue on Apr 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions