Zemit\Mvc\Controller\Rest\Actions\DeleteAction

Complexity

Total Complexity

2

Size/Duplication

Total Lines	24
Duplicated Lines	0 %

Test Coverage

Coverage

0%

Importance

Changes	1
Bugs	0	Features	0

1 Method

Rating	Name	Duplication	Size	Complexity
A	deleteAction()	0	16	2

<?php

/**
 * This file is part of the Zemit Framework.
 *
 * (c) Zemit Team <contact@zemit.com>
 *
 * For the full copyright and license information, please view the LICENSE.txt
 * file that was distributed with this source code.
 */

namespace Zemit\Mvc\Controller\Rest\Actions;

use Phalcon\Http\ResponseInterface;
use Zemit\Mvc\Controller\AbstractTrait\AbstractInjectable;
use Zemit\Mvc\Controller\Rest\Response;

trait DeleteAction
{
    use AbstractInjectable;
    use Response;
    
    /**
     * Deleting a record
     */
    public function deleteAction(string|int $id = null): ResponseInterface
    {
        $entity = $this->getSingle($id);

It seems like getSingle() must be provided by classes using this trait. How about adding it as abstract method to this trait?

        
        if (!$entity) {
            return $this->setRestErrorResponse(404);
        }
        
        $delete = $entity->delete();
        $this->view->setVars([

The property view does not exist on Zemit\Mvc\Controller\Rest\Actions\DeleteAction. Did you mean view;?

            'delete' => $delete,
            'single' => $this->expose($entity),

It seems like expose() must be provided by classes using this trait. How about adding it as abstract method to this trait?

            'messages' => $entity->getMessages(),
        ]);
        
        return $this->setRestResponse($delete);
    }
}