UseCase is a library that provides facilities to manage technical code over a Use Case in a Clean / Hexagonal / Use Case Architecture.
- Security access
- Cache management
- Transactional context
- Events
The goal is to have only functional code on the Use Case and manage technical code in an elegant way using annotations.
More details on :
composer require openclassrooms/use-case
or by adding the package to the composer.json file directly.
{
"require": {
"openclassrooms/use-case": "*"
}
}
<?php
require 'vendor/autoload.php';
use OpenClassrooms\UseCase\Application\Services\Proxy\UseCases\UseCaseProxy;
//do things
The UseCaseProxy needs a lot of dependencies.
The Dependency Injection Pattern is clearly helpful.
For an implementation with Symfony2, the UseCaseBundle is more appropriate.
UseCaseProxy can be instantiate as following:
class app()
{
/**
* @var OpenClassrooms\UseCase\Application\Services\Proxy\UseCases\UseCaseProxyBuilder
*/
private $builder;
/**
* @var OpenClassrooms\UseCase\Application\Services\Security\Security;
*/
private $security;
/**
* @var OpenClassrooms\Cache\Cache\Cache;
*/
private $cache;
/**
* @var OpenClassrooms\UseCase\Application\Services\Transaction\Transaction;
*/
private $transaction;
/**
* @var OpenClassrooms\UseCase\Application\Services\EventSender\EventSender;
*/
private $event;
/**
* @var OpenClassrooms\UseCase\Application\Services\EventSender\EventFactory
*/
private $eventFactory;
/**
* @var Doctrine\Common\Annotations\Reader
*/
private $reader;
public function method()
{
$useCase = $this->builder
->create(new OriginalUseCase())
->withReader($this->reader)
->withSecurity($this->security)
->withCache($this->cache)
->withTransaction($this->transaction)
->withEvent($this->event)
->withEventFactory($this->eventFactory)
->build();
}
}
Only UseCaseProxyBuilder::create(UseCase $useCase)
and UseCaseProxyBuilder::withReader(AnnotationReader $reader)
are mandatory.
A classic Use Case in Clean / Hexagonal / Use Case Architecture style looks like this:
use OpenClassrooms\UseCase\BusinessRules\Requestors\UseCase;
use OpenClassrooms\UseCase\BusinessRules\Requestors\UseCaseRequest;
use OpenClassrooms\UseCase\BusinessRules\Responders\UseCaseResponse;
class AUseCase implements UseCase
{
/**
* @return UseCaseResponse
*/
public function execute(UseCaseRequest $useCaseRequest)
{
// do things
return $useCaseResponse;
}
}
The library provides a Proxy of the UseCase.
@security annotation allows to check access.
use OpenClassrooms\UseCase\BusinessRules\Requestors\UseCase;
use OpenClassrooms\UseCase\BusinessRules\Requestors\UseCaseRequest;
use OpenClassrooms\UseCase\BusinessRules\Responders\UseCaseResponse;
use OpenClassrooms\UseCase\Application\Annotations\Security;
class AUseCase implements UseCase
{
/**
* @security (roles = "ROLE_1")
* @return UseCaseResponse
*/
public function execute(UseCaseRequest $useCaseRequest)
{
// do things
return $useCaseResponse;
}
}
"roles" is mandatory.
Other options :
/**
* @security (roles = "ROLE_1, ROLE_2")
* Check the array of roles
*
* @security (roles = "ROLE_1", checkRequest = true)
* Check access for the object $useCaseRequest
*
* @security (roles = "ROLE_1", checkField = "fieldName")
* Check access for the field "fieldName" of the object $useCaseRequest
*/
@cache annotation allows to manage cache.
use OpenClassrooms\UseCase\BusinessRules\Requestors\UseCase;
use OpenClassrooms\UseCase\BusinessRules\Requestors\UseCaseRequest;
use OpenClassrooms\UseCase\BusinessRules\Responders\UseCaseResponse;
use OpenClassrooms\UseCase\Application\Annotations\Cache;
class AUseCase implements UseCase
{
/**
* @cache
* @return UseCaseResponse
*/
public function execute(UseCaseRequest $useCaseRequest)
{
// do things
return $useCaseResponse;
}
}
The key is equal to : md5(serialize($useCaseRequest))
and the TTL is the default one.
Other options:
/**
* @cache (lifetime=1000)
* Add a TTL of 1000 seconds
*
* @cache (namespacePrefix="namespace_prefix")
* Add a namespace to the id with a namespace id equals to "namespace_prefix"
*
* @cache (namespacePrefix="namespace prefix", namespaceAttribute="fieldName")
* Add a namespace to the id with a namespace id equals to "namespace_prefix" . "$useCaseRequest->fieldName"
*/
Transaction gives a transactional context around the Use Case.
- begin transaction
- execute()
- commit
- rollback on exception
Will use the previous active transaction if there is one.
use OpenClassrooms\UseCase\BusinessRules\Requestors\UseCase;
use OpenClassrooms\UseCase\BusinessRules\Requestors\UseCaseRequest;
use OpenClassrooms\UseCase\BusinessRules\Responders\UseCaseResponse;
use OpenClassrooms\UseCase\Application\Annotations\Transaction;
class AUseCase implements UseCase
{
/**
* @transaction
* @return UseCaseResponse
*/
public function execute(UseCaseRequest $useCaseRequest)
{
// do things
return $useCaseResponse;
}
}
@event annotation allows to send events.
An implementation of OpenClassrooms\UseCase\Application\Services\EventSender\EventFactory must be written in the application context.
use OpenClassrooms\UseCase\BusinessRules\Requestors\UseCase;
use OpenClassrooms\UseCase\BusinessRules\Requestors\UseCaseRequest;
use OpenClassrooms\UseCase\BusinessRules\Responders\UseCaseResponse;
use OpenClassrooms\UseCase\Application\Annotations\EventSender;
class AUseCase implements UseCase
{
/**
* @event
* @return UseCaseResponse
*/
public function execute(UseCaseRequest $useCaseRequest)
{
// do things
return $useCaseResponse;
}
}
The message can be send:
- pre execute
- post execute
- on exception or all of them.
Post is default.
The name of the event is the name of the use case with underscore, prefixed by the method. For previous example, the name would be : use_case.post.a_use_case
Prefixes can be :
- use_case.pre.
- use_case.post.
- use_case.exception.
/**
* @event(name="event_name")
* Send an event with event name equals to *prefix*.event_name
* (note: the name is always converted to underscore)
*
* @event(methods="pre")
* Send an event before the call of UseCase->execute()
*
* @event(methods="pre, post, onException")
* Send an event before the call of UseCase->execute(), after the call of UseCase->execute() or on exception
*/
The execution order is the following:
Pre Excecute:
- security
- cache (fetch)
- transaction (begin transaction)
- event (pre)
Post Excecute:
- cache (save if needed)
- transaction (commit)
- event (post)
On Exception:
- transaction (rollback)
- event (on exception)