These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more
1 | <?php |
||
2 | |||
3 | namespace Nip\Inflector\Traits; |
||
4 | |||
5 | /** |
||
6 | * Trait InflectionTableizeTrait |
||
7 | * @package Nip\Inflector\Traits |
||
8 | * |
||
9 | * @method tableize($string) |
||
10 | */ |
||
11 | trait InflectionTableizeTrait |
||
12 | { |
||
13 | |||
14 | /** |
||
15 | * Converts a class name to its table name according to rails |
||
16 | * naming conventions. |
||
17 | * |
||
18 | * Converts "Person" to "people" |
||
19 | * |
||
20 | * @param string $class_name Class name for getting related table_name. |
||
21 | * @return string plural_table_name |
||
22 | */ |
||
23 | protected function doTableize($class_name) |
||
24 | { |
||
25 | return $this->pluralize($this->underscore($class_name)); |
||
0 ignored issues
–
show
It seems like
pluralize() 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 Adding the
Loading history...
|
|||
26 | } |
||
27 | } |
||
28 |
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
Idable
provides a methodequalsId
that 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.