and let’s assume the following content of Bar.php:
// Bar.phpnamespaceOtherDir;useSomeDir\Foo;// This now conflicts the class OtherDir\Foo
If both files OtherDir/Foo.php and SomeDir/Foo.php are loaded in the
same runtime, you will see a PHP error such as the following:
PHP Fatal error: Cannot use SomeDir\Foo as Foo because the name is already in use in OtherDir/Foo.php
However, as OtherDir/Foo.php does not necessarily have to be loaded and the
error is only triggered if it is loaded before OtherDir/Bar.php, this problem
might go unnoticed for a while. In order to prevent this error from surfacing,
you must import the namespace with a different alias:
// Bar.phpnamespaceOtherDir;useSomeDir\FooasSomeDirFoo;// There is no conflict anymore.
Loading history...
10
use Lcobucci\JWT\Builder;
11
use Lcobucci\JWT\Signer\Hmac\Sha256;
12
use Lcobucci\JWT\Parser;
13
use Lcobucci\JWT\Token;
14
15
abstract class HelperBase
16
{
17
/**
18
* @var array
19
*/
20
protected $config = [];
21
22
/**
23
* Constructor
24
* @param array $config
25
*/
26
31
public function __construct(array $config = [])
27
{
28
31
$this->config = $config;
29
31
if (empty($this->config['secret'])) {
30
1
throw new InvalidTokenException("JWT token generator requires a secret");
31
}
32
30
}
33
34
/**
35
* Checks for all required claims
36
*
37
* @param array $claimKeys
38
* @return boolean
39
*/
40
28
final protected function checkRequiredClaims($claimKeys)
canis-io /
lumen-jwt-auth
Let’s assume that you have a directory layout like this:
. |-- OtherDir | |-- Bar.php | `-- Foo.php `-- SomeDir `-- Foo.phpand let’s assume the following content of
Bar.php:If both files
OtherDir/Foo.phpandSomeDir/Foo.phpare loaded in the same runtime, you will see a PHP error such as the following:PHP Fatal error: Cannot use SomeDir\Foo as Foo because the name is already in use in OtherDir/Foo.phpHowever, as
OtherDir/Foo.phpdoes not necessarily have to be loaded and the error is only triggered if it is loaded beforeOtherDir/Bar.php, this problem might go unnoticed for a while. In order to prevent this error from surfacing, you must import the namespace with a different alias: