Completed
Push — master ( 29a805...bdeb81 )
by Eugene
06:00
created

PackerFactory   A

Complexity

Total Complexity 4

Size/Duplication

Total Lines 24
Duplicated Lines 0 %

Coupling/Cohesion

Components 0
Dependencies 5

Test Coverage

Coverage 0%

Importance

Changes 0
Metric Value
dl 0
loc 24
ccs 0
cts 17
cp 0
rs 10
c 0
b 0
f 0
wmc 4
lcom 0
cbo 5

1 Method

Rating   Name   Duplication   Size   Complexity  
A create() 0 21 4
1
<?php
2
3
/**
4
 * This file is part of the Tarantool Client package.
5
 *
6
 * (c) Eugene Leonovich <[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
declare(strict_types=1);
13
14
namespace Tarantool\Client\Packer;
15
16
use MessagePack\BufferUnpacker;
17
use MessagePack\Packer;
0 ignored issues
show
Bug introduced by
This use statement conflicts with another class in this namespace, Tarantool\Client\Packer\Packer.

Let’s assume that you have a directory layout like this:

.
|-- OtherDir
|   |-- Bar.php
|   `-- Foo.php
`-- SomeDir
    `-- Foo.php

and let’s assume the following content of Bar.php:

// Bar.php
namespace OtherDir;

use SomeDir\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.php
namespace OtherDir;

use SomeDir\Foo as SomeDirFoo; // There is no conflict anymore.
Loading history...
18
use MessagePack\PackOptions;
19
use MessagePack\UnpackOptions;
20
use Tarantool\Client\Packer\Extension\DecimalExtension;
21
use Tarantool\Client\Packer\Packer as ClientPacker;
22
23
final class PackerFactory
24
{
25
    public static function create() : ClientPacker
26
    {
27
        if (\class_exists(BufferUnpacker::class)) {
28
            if (!\extension_loaded('decimal')) {
29
                return new PurePacker();
30
            }
31
32
            $extensions = [new DecimalExtension()];
33
34
            return new PurePacker(
35
                new Packer(PackOptions::FORCE_STR, $extensions),
36
                new BufferUnpacker('', UnpackOptions::BIGINT_AS_DEC, $extensions)
37
            );
38
        }
39
40
        if (\extension_loaded('msgpack')) {
41
            return new PeclPacker();
42
        }
43
44
        throw new \Error('None of the supported msgpack packages were found. To install one, run "composer require rybakit/msgpack"');
0 ignored issues
show
Unused Code introduced by
The call to Error::__construct() has too many arguments starting with 'None of the supported m...quire rybakit/msgpack"'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
45
    }
46
}
47