primasoftware/doctrine-specification

Specification Pattern for your Doctrine repositories

Monday, November 20, 2017
by cdomigan
Repository
1 Watchers
0 Stars
1,057 Installations

PHP
0 Dependents
0 Suggesters
30 Forks
0 Open issues
21 Versions
10 % Grown

The README.md

Happyr Doctrine Specification

, _(*1)

This library gives you a new way for writing queries. Using the Specification pattern you will get small Specification classes that are highly reusable., _(*2)

The problem with writing Doctrine queries is that it soon will be messy. When your application grows you will have 20+ function in your Doctrine repositories. All with long and complicated QueryBuilder calls. You will also find that you are using a lot of parameters to the same method to accommodate different use cases., _(*3)

After a discussion with Kacper Gunia on Sound of Symfony podcast about how to test your Doctrine repositories properly, we (Kacper and Tobias) decided to create this library. We have been inspired by Benjamin Eberlei's thoughts in his blog post., _(*4)

Motivation and basic understanding (this page)
Usage examples
Create your own spec
Contributing to the library

Why do we need this lib?

You are probably wondering why we created this library. Your entity repositories are working just fine as they are, right?, _(*5)

But if your friend open one of your repository classes he/she would probably find that the code is not as perfect as you thought. Entity repositories have a tendency to get messy. Problems may include:, _(*6)

Too many functions (findActiveUser, findActiveUserWithPicture, findUserToEmail, etc)
Some functions have too many arguments
Code duplication
Difficult to test

Requirements of the solution

The solution should have the following features:, _(*7)

Easy to test
Easy to extend, store and run
Re-usable code
Single responsibility principle
Hides the implementation details of the ORM. (This might seen like nitpicking, however it leads to bloated client code doing the query builder work over and over again.)

The practical differences

This is an example of how you use the lib. Say that you want to fetch some Adverts and close them. We should select all Adverts that have their endDate in the past. If endDate is null make it 4 weeks after the startDate., _(*8)

``` php // Not using the lib $qb = $this->em->getRepository('HappyrRecruitmentBundle:Advert') ->createQueryBuilder('r');, _(*9)

return $qb->where('r.ended = 0') ->andWhere( $qb->expr()->orX( 'r.endDate < :now', $qb->expr()->andX( 'r.endDate IS NULL', 'r.startDate < :timeLimit' ) ) ) ->setParameter('now', new \DateTime()) ->setParameter('timeLimit', new \DateTime('-4weeks')) ->getQuery() ->getResult();, _(*10)


``` php
// Using the lib
$spec = Spec::andX(
    Spec::eq('ended', 0),
    Spec::orX(
        Spec::lt('endDate', new \DateTime()),
        Spec::andX(
            Spec::isNull('endDate'),
            Spec::lt('startDate', new \DateTime('-4weeks'))
        )
    )
);

return $this->em->getRepository('HappyrRecruitmentBundle:Advert')->match($spec);

Yes, it looks pretty much the same. But the later is reusable. Say you want another query to fetch Adverts that we should close but only for a specific company., _(*11)

Doctrine Specification

``` php class AdvertsWeShouldClose extends BaseSpecification { public function getSpec() { return Spec::andX( Spec::eq('ended', 0), Spec::orX( Spec::lt('endDate', new \DateTime()), Spec::andX( Spec::isNull('endDate'), Spec::lt('startDate', new \DateTime('-4weeks')) ) ) ); } }, _(*12)

class OwnedByCompany extends BaseSpecification { private $companyId;, _(*13)

public function __construct(Company $company, $dqlAlias = null)
{
    parent::__construct($dqlAlias);
    $this->companyId = $company->getId();
}

public function getSpec()
{
    return Spec::andX(
        Spec::join('company', 'c'),
        Spec::eq('id', $this->companyId, 'c')
    );
}

}, _(*14)

class SomeService { /** * Fetch Adverts that we should close but only for a specific company */ public function myQuery(Company $company) { $spec = Spec::andX( new AdvertsWeShouldClose(), new OwnedByCompany($company) );, _(*15)

    return $this->em->getRepository('HappyrRecruitmentBundle:Advert')->match($spec);
}

}, _(*16)


#### QueryBuilder

If you were about to do the same thing with only the QueryBuilder it would look like this:

``` php
class AdvertRepository extends EntityRepository
{
    protected function filterAdvertsWeShouldClose($qb)
    {
        return $qb
            ->andWhere('r.ended = 0')
            ->andWhere(
                $qb->expr()->orX(
                    'r.endDate < :now',
                    $qb->expr()->andX('r.endDate IS NULL', 'r.startDate < :timeLimit')
                )
            )
            ->setParameter('now', new \DateTime())
            ->setParameter('timeLimit', new \DateTime('-4weeks'))
        ;
    }

    protected function filterOwnedByCompany($qb, Company $company)
    {
        return $qb
            ->join('company', 'c')
            ->andWhere('c.id = :company_id')
            ->setParameter('company_id', $company->getId())
        ;
    }

    public function myQuery(Company $company)
    {
        $qb = $this->em->getRepository('HappyrRecruitmentBundle:Advert')->createQueryBuilder('r');
        $this->filterAdvertsWeShouldClose($qb)
        $this->filterOwnedByCompany($qb, $company)

        return $qb->getQuery()->getResult();
    }
}

The issues with the QueryBuilder implementation are:, _(*17)

You may only use the filters filterOwnedByCompany and filterAdvertsWeShouldClose inside AdvertRepository.
You can not build a tree with And/Or/Not. Say that you want every Advert but not those owned by $company. There is no way to reuse filterOwnedByCompany() in that case.
Different parts of the QueryBuilder filtering cannot be composed together, because of the way the API is created. Assume we have a filterGroupsForApi() call, there is no way to combine it with another call filterGroupsForPermissions(). Instead reusing this code will lead to a third method filterGroupsForApiAndPermissions().

Continue reading

You may want to take a look at some usage examples or find out how to create your own spec., _(*18)

The Versions

20/11 2017

dev-master

9999999-dev http://developer.happyr.com/

Specification Pattern for your Doctrine repositories

library doctrine-specification

Specification Pattern for your Doctrine repositories

primasoftware/doctrine-specification

The README.md

Happyr Doctrine Specification

Table of contents

Why do we need this lib?

Requirements of the solution

The practical differences

Doctrine Specification

Continue reading

The Versions

dev-master

The Requires

The Development Requires

by Tobias Nyholm

by Kacper Gunia

by Chris Domigan

0.13

The Requires

The Development Requires

by Tobias Nyholm

by Kacper Gunia

by Chris Domigan

0.12

The Requires

The Development Requires

by Tobias Nyholm

by Kacper Gunia

by Chris Domigan

0.11

The Requires

The Development Requires

by Tobias Nyholm

by Kacper Gunia

by Chris Domigan

0.10

The Requires

The Development Requires

by Tobias Nyholm

by Kacper Gunia

by Chris Domigan

0.9

The Requires

The Development Requires

by Tobias Nyholm

by Kacper Gunia

by Chris Domigan

0.8.2

The Requires

The Development Requires

by Tobias Nyholm

by Kacper Gunia

by Chris Domigan

0.8.1

The Requires

The Development Requires

by Tobias Nyholm

by Kacper Gunia

by Chris Domigan

0.8.0

The Requires

The Development Requires

by Tobias Nyholm

by Kacper Gunia

by Chris Domigan

0.7.1

The Requires

The Development Requires

by Tobias Nyholm

by Kacper Gunia

0.7.0

The Requires

The Development Requires

by Tobias Nyholm

by Kacper Gunia

0.6.2

The Requires

The Development Requires

by Tobias Nyholm