SerializeAwareTrait   A
last analyzed

Complexity

Total Complexity 2

Size/Duplication

Total Lines 27
Duplicated Lines 0 %

Coupling/Cohesion

Components 0
Dependencies 0

Test Coverage

Coverage 100%

Importance

Changes 1
Bugs 0 Features 1
Metric Value
c 1
b 0
f 1
dl 0
loc 27
wmc 2
lcom 0
cbo 0
ccs 5
cts 5
cp 1
rs 10

3 Methods

Rating   Name   Duplication   Size   Complexity  
toArray() 0 1 ?
A serialize() 0 4 1
A unserialize() 0 4 1
1
<?php
2
3
namespace Equip\Data\Traits;
4
5
trait SerializeAwareTrait /* implements Serializable */
6
{
7
    /**
8
     * @see \Equip\Data\EntityInterface::toArray()
9
     *
10
     * @return array
11
     */
12
    abstract public function toArray();
13
14
    /**
15
     * @inheritDoc
16
     */
17 1
    public function serialize()
18
    {
19 1
        return serialize($this->toArray());
20
    }
21
22
    /**
23
     * @see \Equip\Data\Traits\ImmutableValueObjectTrait::apply()
24
     *
25
     * @inheritDoc
26
     */
27 1
    public function unserialize($data)
28
    {
29 1
        $this->apply(unserialize($data));
0 ignored issues
show
Bug introduced by
It seems like apply() must be provided by classes using this trait. How about adding it as abstract method to this trait?

This check looks for methods that are used by a trait but not required by it.

To illustrate, let’s look at the following code example

trait Idable {
    public function equalIds(Idable $other) {
        return $this->getId() === $other->getId();
    }
}

The trait Idable provides a method equalsId that in turn relies on the method getId(). If this method does not exist on a class mixing in this trait, the method will fail.

Adding the getId() as an abstract method to the trait will make sure it is available.

Loading history...
30 1
    }
31
}
32