Passing extra parameters to eightpoints/guzzle Client class (Symfony 4)
up vote
0
down vote
favorite
In a Symfony 4 project, I make use of eightpoints/guzzle
bundle to make calls to a remote API. After installing the bundle (and configuring a client in a separate yaml file), I followed this quide to make my client autowired, which works perfectly. Then a extended my client class (i.e. the class descending from the GuzzleHttpClient
, the equivalent of the ApiPaymentClient
class in the above guide) with some higher-level methods that take care of the calls I need, which also works great.
The question is: is there a way to make my client class accept extra parameters? Specifically, I'd like to define a parameter in the parameters
section of my services.yaml
and then bind it to a specific extra parameter in the client class constructor (which will then store the parameter value in a private variable for usage in the methods), i.e.
class MyClient extends GuzzleHttpClient
{
public function __construct($config, $apiKey)
{
parent::__construct($config);
$this->apiKey = $apiKey;
}
/*...*/
}
Originally (i.e. as the result of the above-mentioned guide) the definition of the client service in services.yaml
goes like this:
AppClientMyClient: '@eight_points_guzzle.client.my_client'
which makes sure that MyClient
gets the config defined within the
eight_points_guzzle:
clients:
my_client:
section in the separate bundle config file (eight_points_guzzle.yaml
).
How do I alter the AppClientMyClient
service definition to accept an extra parameter and still get the config from eight_points_guzzle.yaml
? So far I've managed one or the other work, but not both (i.e. making the binding work makes the client definition from eight_points_guzzle.yaml
not be read, and vice versa.)
Bottom line: yes I can define the parameter as a class const in the MyClient class, but I don't like this solution; not mentioning the situation I will one day need to pass a service, not just a simple variable.
guzzle symfony4
add a comment |
up vote
0
down vote
favorite
In a Symfony 4 project, I make use of eightpoints/guzzle
bundle to make calls to a remote API. After installing the bundle (and configuring a client in a separate yaml file), I followed this quide to make my client autowired, which works perfectly. Then a extended my client class (i.e. the class descending from the GuzzleHttpClient
, the equivalent of the ApiPaymentClient
class in the above guide) with some higher-level methods that take care of the calls I need, which also works great.
The question is: is there a way to make my client class accept extra parameters? Specifically, I'd like to define a parameter in the parameters
section of my services.yaml
and then bind it to a specific extra parameter in the client class constructor (which will then store the parameter value in a private variable for usage in the methods), i.e.
class MyClient extends GuzzleHttpClient
{
public function __construct($config, $apiKey)
{
parent::__construct($config);
$this->apiKey = $apiKey;
}
/*...*/
}
Originally (i.e. as the result of the above-mentioned guide) the definition of the client service in services.yaml
goes like this:
AppClientMyClient: '@eight_points_guzzle.client.my_client'
which makes sure that MyClient
gets the config defined within the
eight_points_guzzle:
clients:
my_client:
section in the separate bundle config file (eight_points_guzzle.yaml
).
How do I alter the AppClientMyClient
service definition to accept an extra parameter and still get the config from eight_points_guzzle.yaml
? So far I've managed one or the other work, but not both (i.e. making the binding work makes the client definition from eight_points_guzzle.yaml
not be read, and vice versa.)
Bottom line: yes I can define the parameter as a class const in the MyClient class, but I don't like this solution; not mentioning the situation I will one day need to pass a service, not just a simple variable.
guzzle symfony4
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
In a Symfony 4 project, I make use of eightpoints/guzzle
bundle to make calls to a remote API. After installing the bundle (and configuring a client in a separate yaml file), I followed this quide to make my client autowired, which works perfectly. Then a extended my client class (i.e. the class descending from the GuzzleHttpClient
, the equivalent of the ApiPaymentClient
class in the above guide) with some higher-level methods that take care of the calls I need, which also works great.
The question is: is there a way to make my client class accept extra parameters? Specifically, I'd like to define a parameter in the parameters
section of my services.yaml
and then bind it to a specific extra parameter in the client class constructor (which will then store the parameter value in a private variable for usage in the methods), i.e.
class MyClient extends GuzzleHttpClient
{
public function __construct($config, $apiKey)
{
parent::__construct($config);
$this->apiKey = $apiKey;
}
/*...*/
}
Originally (i.e. as the result of the above-mentioned guide) the definition of the client service in services.yaml
goes like this:
AppClientMyClient: '@eight_points_guzzle.client.my_client'
which makes sure that MyClient
gets the config defined within the
eight_points_guzzle:
clients:
my_client:
section in the separate bundle config file (eight_points_guzzle.yaml
).
How do I alter the AppClientMyClient
service definition to accept an extra parameter and still get the config from eight_points_guzzle.yaml
? So far I've managed one or the other work, but not both (i.e. making the binding work makes the client definition from eight_points_guzzle.yaml
not be read, and vice versa.)
Bottom line: yes I can define the parameter as a class const in the MyClient class, but I don't like this solution; not mentioning the situation I will one day need to pass a service, not just a simple variable.
guzzle symfony4
In a Symfony 4 project, I make use of eightpoints/guzzle
bundle to make calls to a remote API. After installing the bundle (and configuring a client in a separate yaml file), I followed this quide to make my client autowired, which works perfectly. Then a extended my client class (i.e. the class descending from the GuzzleHttpClient
, the equivalent of the ApiPaymentClient
class in the above guide) with some higher-level methods that take care of the calls I need, which also works great.
The question is: is there a way to make my client class accept extra parameters? Specifically, I'd like to define a parameter in the parameters
section of my services.yaml
and then bind it to a specific extra parameter in the client class constructor (which will then store the parameter value in a private variable for usage in the methods), i.e.
class MyClient extends GuzzleHttpClient
{
public function __construct($config, $apiKey)
{
parent::__construct($config);
$this->apiKey = $apiKey;
}
/*...*/
}
Originally (i.e. as the result of the above-mentioned guide) the definition of the client service in services.yaml
goes like this:
AppClientMyClient: '@eight_points_guzzle.client.my_client'
which makes sure that MyClient
gets the config defined within the
eight_points_guzzle:
clients:
my_client:
section in the separate bundle config file (eight_points_guzzle.yaml
).
How do I alter the AppClientMyClient
service definition to accept an extra parameter and still get the config from eight_points_guzzle.yaml
? So far I've managed one or the other work, but not both (i.e. making the binding work makes the client definition from eight_points_guzzle.yaml
not be read, and vice versa.)
Bottom line: yes I can define the parameter as a class const in the MyClient class, but I don't like this solution; not mentioning the situation I will one day need to pass a service, not just a simple variable.
guzzle symfony4
guzzle symfony4
asked Nov 22 at 12:44
Gabi
133
133
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53431336%2fpassing-extra-parameters-to-eightpoints-guzzle-client-class-symfony-4%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown