[DependencyInjection] Don't skip classes with private constructor when autodiscovering #59712
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.
With value objects auto-discovery becoming more mainstream (see #59704), it's time to fix registering classes with private constructors.
Those are skipped today but with support for
#[Autoconfigure(constructor: 'createInstance')]
as introduced in #49665, this doesn't make sense anymore.Best reviewed ignoring whitespace.