Add matchOne to EntitySpecificationRepositoryTrait

[happyr]

Add matchOne to EntitySpecificationRepositoryTrait

[drewclauson]

I would find that useful, as I'm manually checking for that scenario in several cases at this point. An exception would be easier to handle IMHO.

[Nyholm]

Thank you for this suggestion. I like the idea.
If I'm not misremembering there are a way of achieving this. Does the behavior for matchOne differ from using the following?

// Will throw a NoResultException if nothing found
$oneResult = $repo->match(Spec::andX(
  new MySpec(),
  Spec::limit(1)
), Spec::asSingle());

[adamquaile]

I didn't know about that. That would do the trick, except that AsSingle uses Query::HYDRATE_SINGLE_SCALAR so it throws a Doctrine\ORM\NonUniqueResultException for objects.

Changing the hydration mode would be a BC breaking change. Perhaps Spec::asSingle(AsSingle::OBJECT), but then the API is starting to look a bit untidy. What are your thoughts?

[Nyholm]

Lets introduce Spec::asSingleScalar and rewrite Spec::asSingle. Would that work?
Please send a PR if you want to.

[adamquaile]

Yes, that would work. Would you also want matchOne as syntactic sugar for Spec::asSingle, or just the one method?

[Nyholm]

Im not too sure if about introducing matchOne on the EntitySpecificationRepositoryTrait. I want to try to solve problems using Specifications.

[adamquaile]

Okay, no problem.

[Nyholm]

Fixed by #113

[Nyholm]

I've tagged version 0.6.1 which includes this feature.