@@ -28,12 +28,6 @@ Here is a list of features that might convince you to choose this LinkedIn clien
28
28
29
29
## Installation
30
30
31
- Install the library with Composer.
32
-
33
- ``` bash
34
- composer require happyr/linkedin-api-client
35
- ```
36
-
37
31
This library does not have a dependency on Guzzle or any other library that sends HTTP requests. We use the awesome
38
32
HTTPlug to achieve the decoupling. We want you to choose what library to use for sending HTTP requests. Consult this list
39
33
ofthis list virtual packages that support [ php-http/client-implementation] ( https://packagist.org/providers/php-http/client-implementation )
@@ -44,9 +38,22 @@ find clients to use. For more information about virtual packages please refer to
44
38
composer require php-http/guzzle6-adapter
45
39
```
46
40
41
+ You do also need to install a PSR-7 implementation and a factory to create PSR-7 messages (PSR-17 whenever that is
42
+ released). You could use Guzzles PSR-7 implementation and factories from php-http:
43
+
44
+ ``` bash
45
+ composer require guzzlehttp/psr7 php-http/message
46
+ ```
47
+
48
+ Now you may install the library by running the following:
49
+
50
+ ``` bash
51
+ composer require happyr/linkedin-api-client
52
+ ```
53
+
47
54
If you are updating form a previous version make sure to read [ the upgrade documentation] ( Upgrade.md ) .
48
55
49
- ### Finding the HTTP client.
56
+ ### Finding the HTTP client (optional)
50
57
51
58
The LinkedIn client need to know what library you are using to send HTTP messages. You could provide an instance of
52
59
HttpClient and MessageFactory or you could fallback on auto discovery. Below is an example on where you provide a Guzzle6
@@ -59,7 +66,6 @@ $linkedIn->setHttpMessageFactory(new Http\Message\MessageFactory\GuzzleMessageFa
59
66
60
67
```
61
68
62
-
63
69
## Usage
64
70
65
71
In order to use this API client (or any other LinkedIn clients) you have to [ register your application] [ register-app ]
0 commit comments