Skip to content

v4 : Do not require guzzle anymore ? #75

Description

@yched

What problem does your feature request address?

Since v4 allows using a custom HttpClientFactory that is not Guzzle, and simply uses Guzzle as a default,
it would be nice to not force a hard-dependency on "guzzlehttp/guzzle": ">=7" in its composer.json "require" section.
If I'm using a non-Guzzle HttpClientFactory, then I don't need/want Guzzle in my vendor folder ;-)

Maybe it should just list "guzzlehttp/guzzle" in the "suggest" section ?

Describe the desired solution

No response

Alternatives considered

No response

Additional context

No response

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions