These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more
1 | <?php |
||
0 ignored issues
–
show
|
|||
2 | |||
3 | namespace Http\Client\Plugin; |
||
4 | |||
5 | 1 | @trigger_error('The '.__NAMESPACE__.'\AuthenticationPlugin class is deprecated since version 1.1 and will be removed in 2.0. Use Http\Client\Common\Plugin\AuthenticationPlugin instead.', E_USER_DEPRECATED); |
|
0 ignored issues
–
show
It seems like you do not handle an error condition here. This can introduce security issues, and is generally not recommended.
If you suppress an error, we recommend checking for the error condition explicitly: // For example instead of
@mkdir($dir);
// Better use
if (@mkdir($dir) === false) {
throw new \RuntimeException('The directory '.$dir.' could not be created.');
}
Loading history...
|
|||
6 | |||
7 | use Http\Message\Authentication; |
||
8 | use Psr\Http\Message\RequestInterface; |
||
9 | |||
10 | /** |
||
11 | * Send an authenticated request. |
||
12 | * |
||
13 | * @author Joel Wurtz <[email protected]> |
||
14 | * |
||
15 | * @deprecated since since version 1.1, and will be removed in 2.0. Use {@link \Http\Client\Common\Plugin\AuthenticationPlugin} instead. |
||
16 | */ |
||
17 | class AuthenticationPlugin implements Plugin |
||
0 ignored issues
–
show
The interface
Http\Client\Plugin\Plugin has been deprecated with message: since since version 1.1, and will be removed in 2.0. Use {@link \Http\Client\Common\Plugin} instead.
This class, trait or interface has been deprecated. The supplier of the file has supplied an explanatory message. The explanatory message should give you some clue as to whether and when the type will be removed from the class and what other constant to use instead.
Loading history...
|
|||
18 | { |
||
19 | /** |
||
20 | * @var Authentication An authentication system |
||
21 | */ |
||
22 | private $authentication; |
||
23 | |||
24 | /** |
||
25 | * @param Authentication $authentication |
||
26 | */ |
||
27 | 3 | public function __construct(Authentication $authentication) |
|
28 | { |
||
29 | 3 | $this->authentication = $authentication; |
|
30 | 3 | } |
|
31 | |||
32 | /** |
||
33 | * {@inheritdoc} |
||
34 | */ |
||
35 | 1 | public function handleRequest(RequestInterface $request, callable $next, callable $first) |
|
36 | { |
||
37 | 1 | $request = $this->authentication->authenticate($request); |
|
38 | |||
39 | 1 | return $next($request); |
|
40 | } |
||
41 | } |
||
42 |
The PSR-1: Basic Coding Standard recommends that a file should either introduce new symbols, that is classes, functions, constants or similar, or have side effects. Side effects are anything that executes logic, like for example printing output, changing ini settings or writing to a file.
The idea behind this recommendation is that merely auto-loading a class should not change the state of an application. It also promotes a cleaner style of programming and makes your code less prone to errors, because the logic is not spread out all over the place.
To learn more about the PSR-1, please see the PHP-FIG site on the PSR-1.