Completed
Push — v3 ( 862d0b...57b69a )
by Beñat
05:33
created

ResponseDataTransformer::__construct()   A

Complexity

Conditions 2
Paths 2

Size

Total Lines 10
Code Lines 6

Duplication

Lines 0
Ratio 0 %

Importance

Changes 2
Bugs 1 Features 0
Metric Value
c 2
b 1
f 0
dl 0
loc 10
rs 9.4285
cc 2
eloc 6
nc 2
nop 1
1
<?php
2
3
/*
4
 * This file is part of the Stack Exchange Api Client library.
5
 *
6
 * Copyright (c) 2014-2016 Beñat Espiña <[email protected]>
7
 *
8
 * For the full copyright and license information, please view the LICENSE
9
 * file that was distributed with this source code.
10
 */
11
12
namespace BenatEspina\StackExchangeApiClient\Application\DataTransformer;
13
14
use Psr\Http\Message\ResponseInterface as Response;
15
16
/**
17
 * Response data transformer.
18
 *
19
 * @author Beñat Espiña <[email protected]>
20
 */
21
interface ResponseDataTransformer
22
{
23
    /**
24
     * Writes the high level $response concepts.
25
     *
26
     * @param Response $response The response
27
     */
28
    public function write(Response $response);
0 ignored issues
show
Documentation introduced by
For interfaces and abstract methods it is generally a good practice to add a @return annotation even if it is just @return void or @return null, so that implementors know what to do in the overridden method.

For interface and abstract methods, it is impossible to infer the return type from the immediate code. In these cases, it is generally advisible to explicitly annotate these methods with a @return doc comment to communicate to implementors of these methods what they are expected to return.

Loading history...
29
30
    /**
31
     * Reads the low level response infrastructure details.
32
     *
33
     * @return mixed
34
     */
35
    public function read();
36
}
37