Fix uninitialized typed $container error on Symfony Console 8.1#119
Merged
kayw-geek merged 1 commit intoMay 20, 2026
Merged
Conversation
… 8.1 typed $container init error
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
1 participant
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.
Summary
MonorepoBuilderApplication::__constructcalls$this->addCommands($commands)beforeparent::__construct(). Symfony Console 8.1 promoted$containerto a typed constructor-promoted property onApplication, and theaddCommand()→init()→registerContainerServices()path reads$this->container. Reading an uninitialized typed property fatals:Calling
parent::__construct()first resolves it. Always-correct pattern; the old order only happened to work because the parent didn't access a typed property in that path before 8.1.Fixes #118.