I'm trying to build simple service for rendering various types of pages. Basic concept is having something like:
$somePageType = new PageType(...);
$this->get('page.service')->render($somePagetype);
...which would be designed as Strategy pattern. Page types would implement interface with render
method and page.service
would call it. The problem is I'd like to use Doctrine in page type classes. What are my options here? I'd like to avoid creating service for each of these classes. Is that even possible? Is it possible to make them container aware without being services? Possibly, in the future, some page type might need something more than only Doctrine, so I need to keep in mind also that.
Symfony is based on the classic web design pattern known as the MVC architecture, which consists of three levels: The Model represents the information on which the application operates--its business logic. The View renders the model into a web page suitable for interaction with the user.
But, the key difference is that Strategy Pattern is about modifying a behaviour of a context in runtime using strategies, while Template Method Pattern is about following a skeleton implementation of an algorithm and modifying its behaviour by overriding methods of the skeleton class in the subclasses.
Strategy is a behavioral design pattern that lets you define a family of algorithms, put each of them into a separate class, and make their objects interchangeable.
Strategy Pattern is used for Behavioural decisions, while Bridge Pattern is used for Structural decisions. Brigde Pattern separats the abstract elements from the implementation details, while Strategy Pattern is concerned making algorithms more interchangeable.
Services are exactly what you want here. Being able to inject the dependencies for the particular strategy in question. Then injecting the particular strategy into the controller (could also be a dynamic renderer that chooses the strategy at runtime).
ContainerAware is a really bad practice, it couples the object in question to all of the services in the container. Thus, I'd strongly recommend avoiding it.
I'm assuming PageType
is an example of a strategy class. In that case, you could inject the dependencies by the page.service
and you wouldn't need to define the strategies as services.
Each strategy probably depends on different objects and therefore I guess you could make them ContainerAware
. Here's an example how to do it
// This is the page.service class
class MyPageService {
public function render(PageTypeInterface $page_type) {
$page_type->setContainer($this->container);
// do stuff
}
}
// This is the type strategy
class MyStrategyType extends ContainerAware implements PageTypeInterface {
// you can access the container after MyPageService has injected it.
}
So basically each strategy would extend ContainerAware
and the page.service
would inject the container.
EDIT
If all of your strategies are dependant on the same services, I'd inject them instead of the whole container.
class MyPageService {
public function render(PageTypeInterface $page_type) {
$page_type->setService($this->container->get('my_service'));
// do stuff
}
}
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With