Drupal 7 - Symfony - Dependency Injection Documentation

Transcription

1 Drupal 7 - Symfony - Dependency Injection Documentation Release Makina Corpus Dec 22, 2017

2

3 Contents: 1 Getting started Installation Write your first forward-compatible Drupal 8 module Working with event dispatcher A few weird things this modules does you should be aware of Services this Module Provides 5 3 Bringing Symfony 3 Fullstack and Bundles into Drupal Installation Configuration Working with bundles (Symfony 3.x) Other considerations Using Twig For Drupal Installation Usage Using Drupal 8 Forms in Drupal Defining your form Using the form builder Using your forms in menu Using the Symfony Web Debug Toolbar in Drupal Enable the debug and web profiler bundles Add the necessary configuration Next step: have fun! Using Monolog in Drupal Installing monolog Configuring Monolog Using Drupal 8 Path Alias Manager in Drupal Additional features Using Symfony event sucriber for Drupal events Event Classes list Example i

4 10 Introduction Support 27 ii

5 CHAPTER 1 Getting started 1.1 Installation Easy way : if your Drupal 7 project is composer based This module works with composer, and should be installed using it, go in your project repository and just type the following line in your terminal : composer require makinacorpus/drupal-sf-dic Please refer to this Composer template for Drupal projects to have a nice exemple for doing this. Once Composer is installed and autoload dumped, you may add these lines to your settings.php : <? php include_once DRUPAL_ROOT. '/../vendor/autoload.php'; $conf['kernel.cache_dir'] = DRUPAL_ROOT. '/../cache/'; $conf['kernel.logs_dir'] = DRUPAL_ROOT. '/../logs/'; Hard way : if your Drupal 7 project is not composer based You may use the Composer Manager module although it s untested, or if it s not too late you probably should provide a global composer.json for your Drupal site. 1.2 Write your first forward-compatible Drupal 8 module Step 1: Define this module as a dependency Any module relying on it should express it s dependency via the its info file: 1

6 dependencies[] = sf_dic You may also provide a valid composer.json (not required, but it would be a good practice to provide one) Step 2: Define your service Then you just need to write a MYMODULE.services.yml file in your module folder: parameters: mymodule_some_param: 42 services: mymodule_some_service: class: "\MyModule\Class" argument:... # Anything that is Symfony compatible Please refer to Symfony s dependency injection container documentation Step 3: Fetch your services via the Drupal 8 compatibility layer Note: The right way of doing this would be to never use the compatibility layer and introduce all your services via your services definition file. Nevertheless, at some point, you will need to get a specific service in the Drupal 7 oldschool legacy procedural code, in case you would just need to : <? php function mymodule_do_something() { $myservice \MyModule\SomeService */ $myservice = \Drupal::service('mymodule_some_service'); The container itself is supposed to be kept hidden, but if you wish to fetch at some point the container, you might do it this way : <? php function mymodule_do_something() { // The Drupal 8 way. $container = \Drupal::getContainer(); // A more generic way (choose either one, the one upper is prefered). $container \Symfony\Component\DependencyInjection\ContainerInterface */ $container = \Drupal::service('service_container'); // From this point, you might use some parameters given by the various modules // services definitions. $somevalue = $container->getparameter('some_module.some_param'); 2 Chapter 1. Getting started

7 1.2.4 Step 4: Register compiler pass I am sorry for this one, it d need a little bit of magic to make it easy and working at the same time, so here is the arbitrary choose way: In Drupal 8 you can define classes implementing the Drupal\Core\DependencyInjection\ServiceProviderInterface interface, which is also defined by this module. But, because Drupal 7 is not Drupal 8, you will need to arbitrarily write a class named `Drupal\Module\MYMODULE\ServiceProvider` which implements this interface, and write it into the MYMODULE.container.php file. For example, let s say your module name is kitten_killer, you would write the kitten_killer. container.php file containing the following code : <?php // Note that the namespace here contains the lowercased Drupal internal // module name, if you don't, the container builder won't find it. namespace Drupal\Module\kitten_killer; use Drupal\Core\DependencyInjection\ServiceProviderInterface; use Symfony\Component\DependencyInjection\ContainerBuilder; // You MUST NOT change the class name. class ServiceProvider implements ServiceProviderInterface { /** * {@inheritdoc */ public function register(containerbuilder $container) { // From this point you can arbitrarily use the container the way you // wish and register anything you need. $container->addcompilerpass(new MyModule\DependencyInjection\SomeCompilerPass()); 1.3 Working with event dispatcher Create an event subscriber implementing Symfony\Component\EventDispatcher\EventSubscriberInterface then register it in your my_module.services.yml file by adding it the event_subscriber tag : services: my_module_some_event: class: MyVendor\MyModule\EventSubscriber\SomeEventSubscriber tags: [{ name: event_subscriber ] 1.4 A few weird things this modules does you should be aware of Both \Drupal\node\NodeInterface and \Drupal\user\UserInterface are implemented and automatically in use via the Drupal 7 entity controllers but you may also load them using entity storage services 1.3. Working with event dispatcher 3

8 path_inc variable is enforced and you cannot change it using your settings.php file, instead your module should override the path.alias_storage or path.alias_manager services Global $language variable is replaced by a \Drupal\Core\Language\LanguageInterface instance All the Drupal variables are set as a container parameters, which mean that you can use all of them as services parameters. Please note that the side effect of this is that if you wish to change a variable and use the new value as a service parameter, you will need to rebuild the container. And that s pretty much it Not all services can go in the container There is no way to allow this module to get the enabled module list before the DRUPAL_BOOTSTRAP_CONFIGURATION phase (unless you are lucky and caches are set) or before the DRUPAL_BOOTSTRAP_DATABASE phase (because Drupal 7 will need the database to get the module list). That s why the hook_boot() implementation in this module will remain. This means that there is absolutly no way to allow cache backends services to be in the service container, sad, but true story. Long story short: any service you would want to involve in any pre-hook_boot() running code cannot be set in the container Compiled container is a PHP file Which means that if you run Drupal with multiple web heads that don t share the same filesystem, you might experience container desync problems on rebuild. Future plans to solve this is to provide a cache based container such as Drupal 8 does. 4 Chapter 1. Getting started

9 CHAPTER 2 Services this Module Provides Note: This list is not complete, but is updated from time to time, the best way to have a complete list is to read the services.yml file. This modules provides a set of Drupal 8 API-compatible services that you should use in your own Drupal 7 module in order to reduce the future porting time to Drupal 8 : service_container : \Symfony\Component\DependencyInjection\ContainerInterface instance that points to the current container itself request_stack : \Symfony\Component\HttpFoundation\RequestStack instance, yes, a real one in your Drupal 7 database : \DatabaseConnection instance that points to the Drupal default database event_dispatcher : Symfony\Component\EventDispatcher\EventDispatcher which allows you to use it at your convenence; Note: please be aware that only the KernelEvents::TERMINATE event is run as of now (others are not revelant in a Drupal 7 site) entity.manager : \Drupal\Core\Entity\EntityManager passthru that only defines the getstorage($entity_type) method that will return \DrupalEntityControllerInterface instance You can fetch \Drupal\Core\Entity\EntityStorageInterface instances via the entity manager service, which are compatible with Drupal 8 interface module_handler: \Drupal\Core\Extension\ModuleHandler passthru uses Drupal 7 module.inc functions cache_factory : \Drupal\Core\Cache\CacheFactory instance, working as expected 5

10 cache.name (where NAME in bootstrap, default, entity, menu, render, data) : \Drupal\Core\Cache\CacheBackendInterface specific implementation that will proxify toward the Drupal 7 cache layer, fully API compatible with Drupal 8 logger.factory : Drupal\Core\Logger\LoggerChannelFactory compatible service that will allow you to inject loggers into your services instead of using the watchdog function logger.channel.name (where NAME in default, php, image, cron, file, form) : Psr\Log\LoggerInterface instances, also happen to be Drupal\Core\Logger\LoggerChannelInterface implementations form_builder : Drupal\Core\Form\FormBuilder instance, with a single method implemented: getform which allows you to spawn Drupal 8 style forms in your Drupal 7 site, the implementation is transparent current_user : Drupal\Core\Session\AccountProxy compatible with Drupal\Core\Session\AccountInterface which proxifies the current user, note that it also replaces the $GLOBALS['user'] object path.alias_manager : Drupal\Core\Path\AliasManagerInterface that does pretty much the same thing as Drupal 7 does but keeping compatibility path.alias_storage : Drupal\Core\Path\AliasStorageInterface that does pretty much the same thing as Drupal 7 does but keeping compatibility path.current : Drupal\Core\Path\CurrentPathStack that you should always use as your object dependencies whenever you need the current path, instead of using current_path() or $_GET['q'] You should use \Drupal\Core\Session\AccountInterface whenever you need a user account which is not meant to be manipulated as an entity, for example for various access checks 6 Chapter 2. Services this Module Provides

11 CHAPTER 3 Bringing Symfony 3 Fullstack and Bundles into Drupal 7 This module can natively use Symfony bundles into the Drupal application, but you must ackowledge the fact that you cannot use the whole Symfony API : you may use *Bundle class, the Extension class, and provide services via the Resource/config folder; you may use Twig natively (the TwigBundle is automatically registered in the kernel if the classes are found) where template naming convention are the Symfony naming conventions; this module provide an abstract controller class MakinaCorpus\Drupal\Sf\Controller that you may extend in order to provide controllers, you must then now that your controllers won t behave like symfony components, but there return will only be used to fill in the page content Drupal region; use the router component, as any Symfony application, but you must know that controllers will be executed by a specific Drupal menu router callback instead of being run by the HttpKernel. Router usage is disabled per default; you may use anything you want as long as you set it as composer dependencies case in which you might want to see the next chapter. Please note that it will only work to the packages you pulled extend. 3.1 Installation Note: Bringing Symfony 3 Fullstack into Drupal 7 can only work with the Drupal Clean URL function enabled Bringing in required dependencies You must require a few packages for this to work, if you want twig you must : composer require symfony/twig-bundle 7

12 You probably also want to add the twig/extensions package. Alternatively, if you are not afraid and have beard, you could just: composer require symfony/symfony Which should work gracefully, note that we are not using the Symfony full stack so most of its code won t be in use Enable the fullstack framework usage You must use the symfony/symfony package as a dependency, then add the following variables to your settings.php file : <? php $conf['kernel.symfony_all_the_way'] = true; 3.2 Configuration Configuration directory structure (Symfony 3.x) Symfony will need a kernel root directory for loading its configuration and default resources, the commonly seen app folder in Symfony applications. Directory structure when using this module is exactly the same, if the app directory exists as follows : <? php /path/to/project/www/index.php # Where Drupal lives /path/to/project/app You will then find the following directory structure : app/config/config.yml where your configuration is stored; app/config/config_environment.yml in opposition to a common Symfony application, these files are optional and will fallback on the config.yml file, but you may use them; app/config/parameters.yml where your parameters are stored; app/routing.yml where the routing happens; app/resources/ where you may put additional resources, such as Twig template overrides. In case the app directory does not exists, the module will fallback onto the following structure : www/sites/default/config/config.yml; www/sites/default/config/config_environment.yml; www/sites/default/config/parameters.yml; www/sites/default/routing.yml; www/sites/default/resources/. Please also note that if you don t provide any config.yml file, the module will automatically fallback on its own implementation, you might find in : drupal-sf-dic/resources/config/config.yml. 8 Chapter 3. Bringing Symfony 3 Fullstack and Bundles into Drupal 7

13 3.2.2 Configuration directory structure (Symfony 4.x) Symfony will need a kernel root directory for loading its configuration and default resources, the commonly seen config folder in Symfony applications. Directory structure when using this module is exactly the same, if the app directory exists as follows : <? php /path/to/project/public/index.php # Where Drupal lives /path/to/project/config /path/to/project/config/packages /path/to/project/config/bundles.php # Required by Symfony project template /path/to/project/config/src /path/to/project/config/src/controller # Required by Symfony project template /path/to/project/templates # Required by Symfony project template This has yet to be fully documented, but as quick start, just copy the Resources/docs/sample/symfony-4 folder contents into your project root folder. The other steps are optional for Symfony 4, use symfony-flex for bundles auto configuration, and the dotenv component for environment specific configuration Overriding configuration (Symfony 3.x) In order to override the configuration and provide your own, you must copy the following files into the previously mentionned config/ directory : drupal-sf-dic/resources/config/config.yml; drupal-sf-dic/resources/config/parameters.yml. 3.3 Working with bundles (Symfony 3.x) You may, as any Symfony application, provider your own kernel implementation, for this, copy the sample/appkernel.php file and set your own bundles. For it to work, you need the AppKernel.php file to be automatically loaded, for this use composer. Let s consider you placed the file at this location : app/appkernel.php, you may add the following into your composer.json file : { "autoload" : { "files" : [ "app/appkernel.php" ] And then : composer dump-autoload 3.3. Working with bundles (Symfony 3.x) 9

14 3.4 Other considerations Using Symfony for 403 and 404 pages You may use Symfony for your basic error pages, yet Drupal cannot catch exceptions without modifying its source code, we still can catch 403 and 404 errors using the Drupal configuration. For this, you need to go Symfony all the way as described above, then add the following variables into your settings.php file : <? php $conf['site_403'] = 'symfony/access-denied'; $conf['site_404'] = 'symfony/not-found'; Using the router You can use the Symfony router, and build 100% Symfony compatible code, please see current/book/routing.html Register your bundle s services.yml file You must first tell this module you will use the Symfony router by adding the following variable to your settings. php file : <? php $conf['kernel.symfony_router_enable'] = true; Then add a sites/default/routing.yml file, containing : my_bundle: resource: "@MyVendorMyBundle/Resources/config/routing.yml" prefix: / 10 Chapter 3. Bringing Symfony 3 Fullstack and Bundles into Drupal 7

15 CHAPTER 4 Using Twig For Drupal Installation To the twig engine, first install the dependencies with : composer require "symfony/twig-bundle:3.1.*" Note: If you want to use Twig, all the dependencies written above are mandatory, and you must use them in the specified versions. Add engine = twig to your theme info file, rebuild your cache, and that s it. Note: If you plan to inherit from a non twig-theme, you may need the latest patch from Usage Twig template naming convention The only thing you have to know is that any module may provide.html.twig files, and the twig engine will automatically take over it. If you want to do a more advanced twig usage, and benefit from all Twig advanced features, you need to know that all the Drupal provided Twig templates will have the following identifier : [theme module]:name:path/to/file.html.twig 11

16 4.2.2 Other template usage within your twig templates For example, let s say you have the tabouret module defining the tabouret/templates/chaises.html.twig the identifier would then be : module:tabouret:templates/chaise.html.twig If you want to write a twig file extending this one, you may add into your.html.twig file : {% extends 'module:tabouret:templates/chaise.html.twig' % My maginificient HTML code. And you re good to do Twig files from bundles You can use Twig files from bundles, you have to follow the Symgfony Twig usage conventions and it ll work transparently Arbitrary render a template You may just: <? php return sf_dic_twig_render('module:tabouret:templates/chaise.html.twig', ['some' => $variable]); And you re good to go. 12 Chapter 4. Using Twig For Drupal 7

17 CHAPTER 5 Using Drupal 8 Forms in Drupal Defining your form In order to be able to use Drupal 8 style forms, you may spawn them with 2 different methods. First you should define a form implementing FormInterface or extending FormBase. Note: This API is compatible with Drupal 8 so you should read the Drupal 8 documentation. Please notice there are a few missing methods a few differences when dealing with entites and URLs, since Drupal 8 does not handle those the same way as Drupal 7. <?php namespace MyVendor\MyModule; use Drupal\Core\Form\FormBase; use Drupal\Core\Form\FormStateInterface; class MyForm extends FormBase { public function buildform($form, FormStateInterface $form_state) { // build a form API array, classical then return $form; public function submitform(&$form, FormStateInterface $form_state) { // do something... 13

18 5.2 Using the form builder In any kind of code returning a render array, directly call : <?php function my_module_some_page() { $build = []; $build['form'] = \Drupal::formBuilder()->getForm('\\MyVendor\\MyModule'); return $build; 5.3 Using your forms in menu Because we had to hack a bit the way Drupal spawn this forms (don t worry they still are 100% Drupal working forms) if you use the hook menu you must replace the drupal_get_form page callback with sf_dic_page_form in order for it to work, and that s pretty much it : <?php /** * Implements hook_menu(). */ function sf_dic_test_menu() { $items = []; $items['test/form/implements'] = [ 'page callback' => 'sf_dic_page_form', 'page arguments' => ['MakinaCorpus\Drupal\Sf\Tests\Mockup\FormImplements', "42 "], 'access callback' => true, 'type' => MENU_CALLBACK, ]; //... return $items; 14 Chapter 5. Using Drupal 8 Forms in Drupal 7

19 CHAPTER 6 Using the Symfony Web Debug Toolbar in Drupal 7 Warning: Please consider the fact that this remains an experimental feature and it might interfer with some Drupal AJAX queries. If you use the Symfony full stack, and registered the framework bundle, you can now, if you wish, make use of the Symfony profiler and web debug toolbar in Drupal. For this, start with : Bringing Symfony 3 Fullstack and Bundles into Drupal 7 and set-up both Symfony full-stack framework and the router Using Twig For Drupal Enable the debug and web profiler bundles You need to provide your own AppKernel implementation via the app/appkernel.php file. See Working with bundles (Symfony 3.x) for more details about how to provide your own custom kernel. Once you have your own kernel, add this into the registerbundles() method: <? php public function registerbundles() { $bundles = [ new \Symfony\Bundle\FrameworkBundle\FrameworkBundle(), //... ]; if (in_array($this->getenvironment(), ['dev', 'test'], true)) { $bundles[] = new \Symfony\Bundle\DebugBundle\DebugBundle(); 15

20 $bundles[] = new \Symfony\Bundle\WebProfilerBundle\WebProfilerBundle(); return $bundles; 6.2 Add the necessary configuration In the app/config_dev.yml file: framework: router: resource: "%kernel.root_dir%/config/routing_dev.yml" strict_requirements: true profiler: { only_exceptions: false web_profiler: toolbar: true intercept_redirects: false In the app/routing_dev.yml file: _wdt: resource: "@WebProfilerBundle/Resources/config/routing/wdt.xml" prefix: /_wdt _profiler: resource: "@WebProfilerBundle/Resources/config/routing/profiler.xml" prefix: /_profiler _errors: resource: "@TwigBundle/Resources/config/routing/errors.xml" prefix: /_error _main: resource: routing.yml Of course, you need to create those files, or merge them accordingly to what already exists into. 6.3 Next step: have fun! It should be enough for it to work. 16 Chapter 6. Using the Symfony Web Debug Toolbar in Drupal 7

21 CHAPTER 7 Using Monolog in Drupal 7 Warning: This feature is experimental, enable test it before running it in production! Notably, formatting is broken with dblog as of now. This module brings integration for monolog into Drupal 7 with the condition that you use Symfony s FrameworkBundle and MonologBundle, both being registered to you container. For a correct setup please follow the Bringing Symfony 3 Fullstack and Bundles into Drupal 7 documentation first. There is two ways of it setting up: either Drupal is master of logging, and monolog is just a bridge over the Drupal watchdog system; either monolog is master of logging, and this module provides a hook_watchdog() implementation that fowards everything that Drupal catches to monolog. You may use either one or the other, but you cannot use both at the same time. 7.1 Installing monolog First install the Monolog bundle dependency: composer require symfony/monolog-bundle Then add to your AppKernel.php file, in the registerbundles method: <? php new \Symfony\Bundle\MonologBundle\MonologBundle() 17

22 7.2 Configuring Monolog As a bridge to Drupal watchdog Formatter and handler implementations are provided by this module. In order to set it up, you only need to add to you config.yml file : monolog: handlers: drupal: type: service id: drupal.monolog_handler level: warning Note: Of course, you can still add as many handlers as you wish, but beware that since Drupal s watchdog is not bridged to Monolog, Drupal own s errors won t pass into those handlers As the master of things Warning: This is not yet implemented, will come soon! Set into your Drupal s settings.php file : <? php $conf['kernel.symfony_monolog_is_master'] = true; This will enable this module s hook_watchdog() implementation that will bridge all messages to the various Monolog handlers. Please also ensure you disabled all other Drupal logging modules, for example using Drush : drush -y dis dblog syslog You may then proceed with advanced configuration. Advanced configuration Here is a sample config.yml monolog section : monolog: handler: # Per default send everything to the current environment file main: type: stream path: "%kernel.logs_dir%/%kernel.environment%.log" level: debug For a more advanced configuration, please refer to Symfony s manual : Logging with Monolog. 18 Chapter 7. Using Monolog in Drupal 7

23 CHAPTER 8 Using Drupal 8 Path Alias Manager in Drupal 7 This module provides an API-compatible with strictly the same behaviour as the Drupal 8 component with the same name. It overrides the runtime to provides its own path.inc include, which means that you cannot override it anymore. Intead, you MUST override the AliasManager or the AliasStorageInterface components using the dependency injection container. 8.1 Additional features Path alias blacklist You can provide an alias blacklist, which means that no aliases will ever be displayed for entries that match this blacklist. For convenience reasons, existing aliases will still match the original path source, but displaying links using those sources will never use the stored aliases. In order to use this, set the path_alias_blacklist variable, which can be either: a string with path that may contain wildcards (eg. user/*) each string must be separated by a newline character n; an array of strings, each string must be a path that may contain wildcards as well. Internally it uses the drupal_match_path() function for matching the blacklist. 19

24 20 Chapter 8. Using Drupal 8 Path Alias Manager in Drupal 7

25 CHAPTER 9 Using Symfony event sucriber for Drupal events The sf_entity_event submodule essentially provides Symfony events related to Drupal event hooks. 9.1 Event Classes list MakinaCorpus\Drupal\Sf\EventDispatcher\EntityCollectionEvent: EVENT_LOAD: Fired when multiple entities are loaded (hook_entity_load) EVENT_PREPAREVIEW: Fired when multiple entities are prepared for view (hook_entity_prepare_view) MakinaCorpus\Drupal\Sf\EventDispatcher\EntityEvent: EVENT_DELETE: Fired when a single entity is deleted (hook_entity_delete) EVENT_INSERT: Fired when a single entity is inserted (hook_entity_insert) EVENT_PREINSERT: Fired when a single entity is about to be inserted (hook_entity_presave) EVENT_PREPARE: Fired when a single entity is prepared (hook_entity_prepare) EVENT_PREUPDATE: Fired when a single entity is is about to be updated (hook_entity_presave) EVENT_PRESAVE: Fired when a single entity is about to be saved (hook_entity_presave) EVENT_SAVE: Fired when a single entity is saved (hook_entity_save) EVENT_UPDATE: Fired when a single entity is updated (hook_entity_update) EVENT_VIEW: Fired when a single entity is viewed (hook_entity_view) MakinaCorpus\Drupal\Sf\EventDispatcher\NodeAccessEvent: EVENT_NODE_ACCESS: Node access is checked (hook_node_access) MakinaCorpus\Drupal\Sf\EventDispatcher\NodeAccessGrantEvent: EVENT_NODE_ACCESS_GRANT: Node grants are collected for user (hook_node_grants) 21

26 MakinaCorpus\Drupal\Sf\EventDispatcher\NodeAccessRecordEvent: EVENT_NODE_ACCESS_RECORD: Node access record are being collected (hook_node_access_records) MakinaCorpus\Drupal\Sf\EventDispatcher\NodeCollectionEvent: EVENT_LOAD: Fired when multiple nodes are loaded (hook_node_load) MakinaCorpus\Drupal\Sf\EventDispatcher\NodeEvent: EVENT_DELETE: Fired when a single node is deleted (hook_node_delete) EVENT_INSERT: Fired when a single node is inserted (hook_node_insert) EVENT_PREINSERT: Fired when a single node is about to be insertd (hook_node_presave) EVENT_PREPARE: Fired when a single node is prepared (hook_node_prepare) EVENT_PREUPDATE: Fired when a single node is about to be updated (hook_node_presave) EVENT_PRESAVE: Fired when a single node is about to be saved (hook_node_presave) EVENT_SAVE: Fired when a single node is saved (hook_node_save) EVENT_UPDATE: Fired when a single node is updated (hook_node_update) EVENT_VIEW: Fired when a single node is viewed (hook_node_view) 9.2 Example your_module.services.yml: your_module.node_subscriber: public: true class: YourPackage\EventSubscriber\NodeEventSubscriber arguments: ["@database"] tags: [{ name: event_subscriber ] src/eventsubscriber/nodeeventsubscriber.php : <?php namespace YourPackage\EventSubscriber; use MakinaCorpus\Drupal\Sf\EventSubscriber\NodeEvent; class NodeEventSubscriber implements EventSubscriberInterface { /** \DatabaseConnection */ private $db; /** * {@inheritdoc */ static public function getsubscribedevents() { return [ 22 Chapter 9. Using Symfony event sucriber for Drupal events

27 ]; NodeEvent::EVENT_SAVE => [ ['onsave', 0] ], /** * Constructor * \DatabaseConnection $db */ public function construct(\databaseconnection $db) { $this->db = $db; public function onsave(nodeevent $event) { $node = $event->getnode(); // Do something... $this->db->select(/*... */); 9.2. Example 23

28 24 Chapter 9. Using Symfony event sucriber for Drupal events

29 CHAPTER 10 Introduction Drupal-sf-dic is a Drupal 7 module that serves the purpose of bringing the Symfony 3 dependency injection container to Drupal 7 along with a limited Drupal 8 API compatibility layer. This project has been maturing enough to fill those needs : Brings the Symfony 3 dependency injection container to Drupal 7 ; Brings a Drupal 8 forward-compatibility layer for easier module porting ; Brings the ability to use Symfony bundles into Drupal 7 as long as they use a limited set of Symfony features. 25

30 26 Chapter 10. Introduction

31 CHAPTER 11 Support Please ask questions on the Github issues page. 27