for testing and deploying your application
for finding and fixing issues
for empowering human code reviews
<?php
/*
* This file is part of the Tinyissue package.
*
* (c) Mohamed Alsharaf <[email protected]>
* For the full copyright and license information, please view the LICENSE
* file that was distributed with this source code.
*/
namespace Tinyissue\Model\Traits\Tag;
use Tinyissue\Model\Tag;
/**
* CrudTrait is trait class containing the methods for adding/editing/deleting the Tag model.
* @author Mohamed Alsharaf <[email protected]>
* @property static $this
trait CrudTrait
{
* Create a new tag.
* @param array $input
* @return mixed
public function createTag(array $input)
$input['group'] = !array_key_exists('group', $input) ? 0 : $input['group'];
return $this->fill($input)->save();
}
* Delete tag.
* @return bool|null
* @throws \Exception
public function delete()
// Remove kanban tags
\DB::table('projects_kanban_tags')->where('tag_id', '=', $this->id)->delete();
id
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;
// Remove relation to issues
\DB::table('projects_issues_tags')->where('tag_id', '=', $this->id)->delete();
return parent::delete();
abstract public function fill(array $attributes);
satrun77 /
tinyissue
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: