Silverback\ApiComponentBundle\Validator\Constraints\SortableValidator::validate()

Complexity

Conditions	8
Paths	8

Size

Total Lines	28
Code Lines	17

Duplication

Lines	0
Ratio	0 %

Importance

Changes

0

<?php
    public function validate($sortable, Constraint $constraint): void
    {
        if (!$constraint instanceof Sortable) {
            throw new UnexpectedTypeException($constraint, Sortable::class);
        }

        if (!$sortable instanceof SortableInterface) {
            throw new UnexpectedTypeException($sortable, SortableInterface::class);
        }

        if ($sortable->getSort() === null) {
            $collection = $sortable->getSortCollection();
            if (
                $collection === null &&
                $sortable instanceof ComponentLocationEntity &&
                ($dynamicPageClass = $sortable->getDynamicPageClass())
            ) {
                $collection = $this->componentLocationRepository->findBy([
                    'dynamicPageClass' => $dynamicPageClass
                ]);
            }
            $sortable->setSort($sortable->calculateSort(true, $collection));

It seems like $collection can also be of type Silverback\ApiComponentBundle\Entity\Component\ComponentLocation[]; however, parameter $sortCollection of Silverback\ApiComponentBundle\Entity\SortableInterface::calculateSort() does only seem to accept Doctrine\Common\Collections\Collection|null, maybe add an additional type check?

It seems like $collection can also be of type Silverback\ApiComponentBundle\Entity\Component\ComponentLocation[]; however, parameter $sortCollection of Silverback\ApiComponentBundle\Entity\Component\ComponentLocation::calculateSort() does only seem to accept Doctrine\Common\Collections\Collection|null, maybe add an additional type check?

        }

        if ($sortable->getSort() === null) {
            $this->context->buildViolation($constraint->message)
                ->atPath('sort')
                ->addViolation();
        }