at github I found a validator to make sure, that a variable is unique. After implementation I get the error “The option “repository” must implement RepositoryInterface” in the frondend.
In my model the variable to validate looks like that:
if (!$repository instanceof \TYPO3\Flow\Persistence\RepositoryInterface) {
throw new \TYPO3\Flow\Validation\Exception\InvalidValidationOptionsException('The option "repository" must implement RepositoryInterface.', 1336499435);
}
Can anybody give a hint to me how to implement the RepositoryInterface?
Thank you!
Hallo Philipp,
yes, I used the “use \Itoop\Customers\Domain\Repository\CustomerRepository;” statement in the model.
I also tried different annotations in my model, too, for example like this:
Plz debug the isValid of the validator. It seems like the options you apply are strings and no one is making an instance of your repository. Maybe you have to make an instance of the repository (using the objectManager) first.
Good morning Aske,
thank you. This Validator is to validate an entity - I just want to validate, that there’s only one object with the same “company name”.
Now I wrote my own validator, which is completely sufficient for my special case:
<?php
namespace Itoop\Customers\Validation\Validator;
use TYPO3\Flow\Annotations as Flow;
class UniqueCustomerValidator extends \TYPO3\Flow\Validation\Validator\AbstractValidator {
/**
* @Flow\Inject
* @var \Itoop\Customers\Domain\Repository\CustomerRepository
*/
protected $customerRepository;
/**
* This validator always needs to be executed even if the given value is empty.
* See AbstractValidator::validate()
*
* @var boolean
*/
protected $acceptsEmptyValues = FALSE;
/**
* @param mixed $value The value that should be validated
* @return void
* @throws \TYPO3\Flow\Validation\Exception\InvalidValidationOptionsException
*
*
*/
protected function isValid($value) {
if(empty($value)) {
$this->addError('Dieses Feld darf nicht leer sein.', 1456984915);
}
$query = $this->customerRepository->createQuery();
$numberOfResults = $query->matching($query->equals('company', $value))->count();
if ($numberOfResults > 0) {
$message = "Eine Firma mit dem Namen \"$value\" existiert schon.";
$this->addError($message, 1456983326);
}
}
}
?>
the snippet was quite old indeed. But it should work nevertheless. It was just meant to be used in conjunction with the Flow Form Framework where it’s possible to use complex types in validator options.
I’ve just updated the gist to allow class names, too.
But using your custom validator makes a lot of sense here anyways.
PS: One more remark. If a company name must be unique, you might want to make it part of the identity (or at least specify a unique constraint like @ORM\Table(uniqueConstraints={@ORM\UniqueConstraint(name="company_unique", columns={"company"})})
I always get a whitescreen and the apache-logfile says something like that:
PHP Fatal error: Class 'CustomerRepository' not found in /var/www/html/customers/Data/Temporary/Development/Cache/Code/Flow_Object_Classes/Itoop_Customers_Validation_Validator_UniqueValidator.php on line 19
Line 19 is this:
$repository = new $this->options['repository']()
Although maybe it’s a trivial question: Which exact annotation options do I have to use? I think the propertyName should be correct, but at the repository I’m not sure.
PS.: If the class “customer” in my model is already marked as entity like the following - the property company should be part of the identity already, should’nt it?
<?php
namespace Itoop\Customers\Domain\Model;
/*
* This file is part of the Itoop.Customers package.
*/
use Doctrine\Common\Collections\ArrayCollection;
use Doctrine\Common\Collections\Collection;
use TYPO3\Flow\Annotations as Flow;
use Doctrine\ORM\Mapping as ORM;
/**
* @Flow\Entity
*/
class Customer
{
/**
* @var string
*/
protected $customernumber;
/**
* @var string
* @Flow\Validate(type="Itoop.Customers:Unique", options={ "repository"="CustomerRepository", "propertyName"="company" })
*/
protected $company;
I tried it with Itoop\Customers\Repository\CustomerRepository as namespace - so I think I forgot Domain\ in the namespace, sorry
I´ll try it later with the correct namespace Itoop\Customers\Domain\Repository\CustomerRepository.
Which is exactly what the unique entity validator does, hence why I mentioned it to you. You don’t need to write a custom validator to achieve what you need.
