| Conditions | 1 |
| Paths | 1 |
| Total Lines | 10 |
| Code Lines | 4 |
| Lines | 0 |
| Ratio | 0 % |
| Tests | 0 |
| CRAP Score | 2 |
| Changes | 2 | ||
| Bugs | 1 | Features | 0 |
| 1 | <?php |
||
| 47 | public function delete() |
||
| 48 | { |
||
| 49 | // Remove kanban tags |
||
| 50 | \DB::table('projects_kanban_tags')->where('tag_id', '=', $this->id)->delete(); |
||
| 51 | |||
| 52 | // Remove relation to issues |
||
| 53 | \DB::table('projects_issues_tags')->where('tag_id', '=', $this->id)->delete(); |
||
| 54 | |||
| 55 | return parent::delete(); |
||
| 56 | } |
||
| 57 | } |
||
| 58 |
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
The trait
Idableprovides a methodequalsIdthat in turn relies on the methodgetId(). 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.