for testing and deploying your application
for finding and fixing issues
for empowering human code reviews
<?php
namespace Encore\Admin\Form\Field;
trait PlainInput
{
protected $prepend;
protected $append;
public function prependIcon($icon, $class = "")
if (is_null($this->prepend)) {
$this->prepend = '<i class="fa fa-' . $icon . " " . $class . '"></i>';
}
return $this;
public function appendIcon($icon, $class = "")
if (is_null($this->append)) {
$this->append = '<i class="fa fa-' . $icon . " " . $class . '"></i>';
public function prepend($string)
$this->prepend = $string;
public function append($string)
$this->append = $string;
protected function initPlainInput()
if (empty($this->view)) {
$this->view = 'admin::form.input';
view
In PHP it is possible to write to properties without declaring them. For example, the following is perfectly valid PHP code:
class MyClass { } $x = new MyClass(); $x->foo = true;
Generally, it is a good practice to explictly declare properties to avoid accidental typos and provide IDE auto-completion:
class MyClass { public $foo; } $x = new MyClass(); $x->foo = true;
protected function defaultAttribute($attribute, $value)
if (!array_key_exists($attribute, $this->attributes)) {
attributes
$this->attribute($attribute, $value);
attribute()
Encore\Admin\Form\Field\PlainInput
defaultAttribute()
This check marks calls to methods that do not seem to exist on an object.
This is most likely the result of a method being renamed without all references to it being renamed likewise.
In PHP it is possible to write to properties without declaring them. For example, the following is perfectly valid PHP code:
Generally, it is a good practice to explictly declare properties to avoid accidental typos and provide IDE auto-completion: