Completed
Pull Request — develop (#70)
by Ionut
02:19
created

Transactionable::update()   A

Complexity

Conditions 2
Paths 2

Size

Total Lines 16
Code Lines 9

Duplication

Lines 0
Ratio 0 %

Importance

Changes 1
Bugs 0 Features 0
Metric Value
c 1
b 0
f 0
dl 0
loc 16
rs 9.4285
cc 2
eloc 9
nc 2
nop 2
1
<?php
2
3
/*
4
*
5
* NOTICE OF LICENSE
6
*
7
 * Part of the Rinvex Repository Package.
8
 *
9
 * This source file is subject to The MIT License (MIT)
10
* that is bundled with this package in the LICENSE file.
11
 *
12
 * Package: Rinvex Repository Package
13
* License: The MIT License (MIT)
14
* Link:    https://rinvex.com
15
 */
16
17
namespace Rinvex\Repository\Traits;
18
19
trait Transactionable
20
{
21
    /**
22
     * Create a new entity with the given attributes.
23
     *
24
     * @param array $attributes
25
     *
26
     * @throws \Exception
27
     *
28
     * @return array
29
     */
30
    public function create(array $attributes = [])
31
    {
32
        // Start transaction!
33
        $this->getContainer('db')->beginTransaction();
0 ignored issues
show
Bug introduced by
It seems like getContainer() 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...
34
        try {
35
            $result = parent::create($attributes);
36
        } catch (\Exception $e) {
37
            // Rollback if something went wrong
38
            $this->getContainer('db')->rollback();
0 ignored issues
show
Bug introduced by
It seems like getContainer() 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...
39
            throw $e;
40
        }
41
        // Commit the queries!
42
        $this->getContainer('db')->commit();
0 ignored issues
show
Bug introduced by
It seems like getContainer() 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...
43
44
        return $result;
45
    }
46
47
    /**
48
     * Update an entity with the given attributes.
49
     *
50
     * @param mixed $id
51
     * @param array $attributes
52
     *
53
     * @throws \Exception
54
     *
55
     * @return array
56
     */
57
    public function update($id, array $attributes = [])
58
    {
59
        // Start transaction!
60
        $this->getContainer('db')->beginTransaction();
0 ignored issues
show
Bug introduced by
It seems like getContainer() 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...
61
        try {
62
            $result = parent::update($id, $attributes);
63
        } catch (\Exception $e) {
64
            // Rollback if something went wrong
65
            $this->getContainer('db')->rollback();
0 ignored issues
show
Bug introduced by
It seems like getContainer() 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...
66
            throw $e;
67
        }
68
        // Commit the queries!
69
        $this->getContainer('db')->commit();
0 ignored issues
show
Bug introduced by
It seems like getContainer() 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...
70
71
        return $result;
72
    }
73
74
    /**
75
     * Delete an entity with the given id.
76
     *
77
     * @param mixed $id
78
     *
79
     * @throws \Exception
80
     *
81
     * @return array
82
     */
83
    public function delete($id)
84
    {
85
        // Start transaction!
86
        $this->getContainer('db')->beginTransaction();
0 ignored issues
show
Bug introduced by
It seems like getContainer() 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...
87
        try {
88
            $result = parent::delete($id);
89
        } catch (\Exception $e) {
90
            // Rollback if something went wrong
91
            $this->getContainer('db')->rollback();
0 ignored issues
show
Bug introduced by
It seems like getContainer() 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...
92
            throw $e;
93
        }
94
        // Commit the queries!
95
        $this->getContainer('db')->commit();
0 ignored issues
show
Bug introduced by
It seems like getContainer() 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...
96
97
        return $result;
98
    }
99
}
100