Problem/Motivation
In Drupal 8 and 9, Drupal had an indirect dependency on guzzlehttp/psr7 because Guzzle uses it internally to create Request and Response objects.
In Drupal 10, numerous core services depend on guzzlehttp/psr7 as our PSR-17 implementation, so we should add a direct dependency and constraint for it.
Proposed resolution
Add a direct dependency on the guzzlehttp/psr7 package.
Remaining tasks
TBD
User interface changes
N/A
API changes
N/A
Data model changes
N/A
Release notes snippet
Drupal core now has a direct dependency on the guzzlehttp/psr7 package (previously an indirect dependency) since it is used for the default implementation of several core services for PSR-17.
Comments
Comment #2
xjmComment #4
xjmComment #5
xjmComment #6
xjmComment #7
spokjeMR:
- Does what it says on the tin: Adding
guzzlehttp/psr7as a direct dependency- TestBot likes it
RTBC for me.
Comment #8
dwwAgreed, MR looks good. Do we do change records for things like this?
Thanks,
-Derek
Comment #9
dwwp.s. This seems more like a task to me. But since @xjm says it's a bug, let's smash it. 😀
Comment #11
catchI added this issue to the existing CR: https://www.drupal.org/node/3256584
Committed 5e03f38 and pushed to 10.0.x. Thanks!
Comment #12
xjm