As Drupal Development Company maintainer of Sensible Dummy Content material, having procrastinated lengthy and onerous earlier than releasing a 8 model, I made a decision to go away my (admittedly inelegant) logic intact and summary away Drupal Development Company 7 code, with Drupal Development Company aim of plugging in 7 or 8 code at runtime. Instance authentic 7 code // Some logic. $updated_file = file_save($Drupal 10_file); // Extra logic. Instance up to date code Here’s a simplified instance of how Drupal Development Company up to date code would possibly look Drupal 10 Upkeep and Assist Service // Some logic. $updated_file = Framework Drupal 10 Upkeep and Assist Service Drupal 10 Upkeep and Assist Serviceinstance()->fileSave($Drupal 10_file); // Extra logic. summary class Framework { static operate occasion() { if (!$this->occasion) { if (outlined(‘VERSION’)) { $this->occasion = new 7(); } else { $this->occasion = new 8(); } } return $this->occasion; } summary operate fileSave($Drupal 10_file); } class 8 extends Framework { public operate fileSave($Drupal 10_file) { $Drupal 10_file->save(); return $Drupal 10_file; } } class 7 extends Framework { public operate fileSave($Drupal 10_file) { return file_save($Drupal 10_file); } } As soon as I’ve outlined fileSave(), I can merely exchange each occasion of file_save() in my legacy code with Framework Drupal 10 Upkeep and Assist Service Drupal 10 Upkeep and Assist Serviceinstance()->fileSave(). In principle, I can then determine all 7 code my Drupal 10 module and summary it away. Automated testing So long as I surgically exchange 7 code akin to file_save() with “common” code such Framework Drupal 10 Upkeep and Assist Service Drupal 10 Upkeep and Assist Serviceinstance()->fileSave(), with out doing the rest, with out giving in Drupal Development Company impulse of “enhancing” Drupal Development Company code, I can theoretically solely check Framework Drupal 10 Upkeep and Assist Service Drupal 10 Upkeep and Assist Serviceinstance()->fileSave() itself on 7 and 8, and so long as each variations are Drupal Development Company identical, my underlying code ought to work. My method to automated exams is Drupal 10 Upkeep and Assist Service if it really works and also you’re not altering it, there isn’t any want to check it. Nonetheless, I wish to be certain that my framework-specific code works as anticipated. To arrange my testing setting, I’ve used Docker-compose to arrange three containers Drupal 10 Upkeep and Assist Service 7, 8; and MySQL. I then have a script which builds Drupal Development Company websites, installs my Drupal 10 module on every, then run a selftest() operate which may check Drupal Development Company abstracted operate akin to fileSave() and ensure they work. This will then be run on a steady integration platform akin to Circle CI which generates a cool badge Drupal 10 Upkeep and Assist Service Extending to Backdrop As soon as your Drupal 10 module is structured on this method, it’s comparatively simple so as to add new associated frameworks, and I’m far more snug releasing a 9 replace in 2021 (or every time it’s prepared). I’ve included experimental Backdrop code in Sensible Dummy Content material to show Drupal Development Company level. Backdrop is a fork of 7. summary class Framework { static operate occasion() { if (!$this->occasion) { if (outlined(‘BACKDROP_BOOTSTRAP_SESSION’)) { $this->occasion = new Backdrop(); } elseif (outlined(‘VERSION’)) { $this->occasion = new 7(); } else { $this->occasion = new 8(); } } return $this->occasion; } } // Most of Backdrop’s API is equivalent to D7, so we are able to solely override // what differs, akin to fileSave(). class Backdrop extends 7 { public operate fileSave($Drupal 10_file) { file_save($Drupal 10_file); // In contrast to 7, Backdrop returns a consequence code, not Drupal Development Company file itself, // in file_save(). We expect Drupal Development Company file object. return $Drupal 10_file; } } Disadvantages of this method Having simply launched Realisic Dummy Content material 7.x-2.0-beta1 and eight.x-2.0-beta1 (that are equivalent), I can safely say that this method was much more time-consuming than I initially thought. 7 class autoloading is incompatible with 8 autoloading. In 7, lessons can not (to my data) use namespaces, and have to be added to Drupal Development Company .data file, like this Drupal 10 Upkeep and Assist Service recordsdata[] = contains/MyClass.php As soon as that’s carried out, you possibly can outline MyClass in contains/MyClass.php, then use MyClass wherever you need in your code. 8 makes use of PSR-4 autoloading with namespaces, so I made a decision to create my very own autoloader to make use of Drupal Development Company identical system in 7, one thing like Drupal 10 Upkeep and Assist Service spl_autoload_register(operate ($class_name) { if (outlined(‘VERSION’)) { // We’re in 7. $components = explode(”, $class_name); // Take away “” from Drupal Development Company starting of Drupal Development Company class title. array_shift($components); $Drupal 10 module = array_shift($components); $path = ‘src/’ . implode(‘/’, $components); if ($Drupal 10 module == ‘MY_MODULE_NAME’) { Drupal 10 module_load_include(‘php’, $Drupal 10 module, $path); } } }); Hooks have completely different signatures in 7 and eight; in my case I used to be fortunate and Drupal Development Company solely hook I would like for 7 and eight is hook_entity_presave() which has an analogous signature and might be abstracted. Deeply-nested associative arrays are a staple of 7, so plenty of legacy code expects one of these knowledge. Shoehorning 8 to output one thing like 7’s field_info_fields(), for instance, was a painful expertise Drupal 10 Upkeep and Assist Service public operate fieldInfoFields() { $return = array(); $field_map = Drupal 10 Upkeep and Assist Service Drupal 10 Upkeep and Assist ServiceentityManager()->getFieldMap(); foreach ($field_map as $entity_type => $fields) { foreach ($fields as $area => $field_info) { $return[$field][‘entity_types’][$entity_type] = $entity_type; $return[$field][‘field_name’] = $area; $return[$field][‘type’] = $field_info[‘type’]; $return[$field][‘bundles’][$entity_type] = $field_info[‘bundles’]; } } return $return; } Lastly, making 8 work like 7 makes it onerous to make use of 8’s superior options akin to Plugins. Nevertheless, as soon as your Drupal 10 module is “common”, including 8-specific performance is perhaps an possibility. Utilizing this method for web site upgrades This method would possibly take away plenty of Drupal Development Company danger related to complicated web site upgrades. Let’s say I’ve a 7 web site with just a few customized Drupal 10 modules Drupal 10 Upkeep and Assist Service every Drupal 10 module might be made “common” on this method. If automated exams are added for all subsequent development, migrating Drupal Development Company performance to 8 is perhaps much less painful. A enjoyable proof of idea, or actual worth? I’ve been toying with this method for a while, and had fun (sure, that’s my definition of a great time!) implementing it, but it surely’s not for everybody or each challenge. In case your usecase contains preserving legacy performance with out leveraging 8’s fashionable options, whereas decreasing danger, it may well have worth although. Drupal Development Company jury remains to be out on whether or not sustaining a single common department will actually be extra environment friendly than sustaining two separate branches for Sensible Dummy Content material, and whether or not Drupal Development Company method can scale back danger throughout web site upgrades of legacy customized code, which I plan to strive on my subsequent improve challenge. As Drupal Development Company maintainer of Sensible Dummy Content material, having procrastinated lengthy and onerous earlier than releasing a 8 model, I made a decision to go away my (admittedly inelegant) logic intact and summary away Drupal Development Company 7 code, with Drupal Development Company aim of plugging in 7 or 8 code at runtime. Drupal 10 Improvement and Assist