feat: integrate composer-dependency-analyser for dependency analysis … #65
Conversation
…and remove legacy Zend aliases Signed-off-by: mmalac <[email protected]>
|
If I'm honest - I do prefer Also, I prefer the approach of adding deps in a |
| // Legacy Zend Framework aliases | ||
| 'aliases' => [ | ||
| LegacyProblemDetailsMiddleware::class => ProblemDetailsMiddleware::class, | ||
| LegacyProblemDetailsNotFoundHandler::class => ProblemDetailsNotFoundHandler::class, | ||
| LegacyProblemDetailsResponseFactory::class => ProblemDetailsResponseFactory::class, | ||
| ], |
There was a problem hiding this comment.
These aliases cannot be dropped in a minor - that's a BC break. They can be stringified to prevent issues though.
| return $deprecatedResponseFactory !== null && $deprecatedResponseFactory !== ResponseFactoryFactory::class; | ||
| return $deprecatedResponseFactory !== null; |
There was a problem hiding this comment.
This is in place for BC with callable response factories - it can't be removed in a minor
|
Thanks for the valuable feedback. I’ll close this PR for now. It’s better to start from the default branch with the composer require checker. |
4 participants
Description
This PR introduces
shipmonk/composer-dependency-analyserto improve dependency management.