opdavies/oliverdavies.uk
1
0
Fork 0
Code Issues 1 Pull requests Projects 1 Releases Packages Wiki Activity Actions

tome export

Browse source
This commit is contained in:
Oliver Davies 2025-05-30 02:14:32 +01:00
parent 52278c3a53
commit 7a52afab5f
960 changed files with 3670 additions and 2229 deletions
Download patch file Download diff file Expand all files Collapse all files

6
content/node.4e0d5cba-13d4-497e-a320-d1236df4dce2.json
View file

@ -82,15 +82,15 @@
],
"body": [
{
"value": "\n <p>I recently made a change to a Drupal project with several custom modules.<\/p>\n\n<p>As part of the change, there was a method that was no longer being used, so I went ahead and removed it.<\/p>\n\n<p>There were no tests for this part of the codebase, and the existing tests were still passing.<\/p>\n\n<p>My change was successfully finished and deployed, including removing the unused method.<\/p>\n\n<p>A few days later, we noticed cron jobs were no longer running on the website.<\/p>\n\n<p>The method I'd removed was attempting to be called from within a different module.<\/p>\n\n<p>Because it no longer existed, it was causing an error and stopping the cron job from running successfully.<\/p>\n\n<p>When I re-added the method, the cron jobs worked again.<\/p>\n\n<p>There were no <code>dependencies<\/code> set in either module's .info.yml file, though that would only prevent you from uninstalling either module.<\/p>\n\n<p>It wouldn't prevent me from deleting code used by another module.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>This is why I've been <a href=\"/daily\/2024\/02\/08\/experimenting-with-architectural-testing\">experimenting with architectural testing<\/a>. To ensure that modules only use their own code and to start enforcing layers within each module.<\/p>\n\n<p>Then, if I had the same situation again, I'd know straight away that there was an issue and not have to wait for the bug to be deployed to production.<\/p>\n\n ",
"value": "\n <p>I recently made a change to a Drupal project with several custom modules.<\/p>\n\n<p>As part of the change, there was a method that was no longer being used, so I went ahead and removed it.<\/p>\n\n<p>There were no tests for this part of the codebase, and the existing tests were still passing.<\/p>\n\n<p>My change was successfully finished and deployed, including removing the unused method.<\/p>\n\n<p>A few days later, we noticed cron jobs were no longer running on the website.<\/p>\n\n<p>The method I'd removed was attempting to be called from within a different module.<\/p>\n\n<p>Because it no longer existed, it was causing an error and stopping the cron job from running successfully.<\/p>\n\n<p>When I re-added the method, the cron jobs worked again.<\/p>\n\n<p>There were no <code>dependencies<\/code> set in either module's .info.yml file, though that would only prevent you from uninstalling either module.<\/p>\n\n<p>It wouldn't prevent me from deleting code used by another module.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>This is why I've been <a href=\"\/daily\/2024\/02\/08\/experimenting-with-architectural-testing\">experimenting with architectural testing<\/a>. To ensure that modules only use their own code and to start enforcing layers within each module.<\/p>\n\n<p>Then, if I had the same situation again, I'd know straight away that there was an issue and not have to wait for the bug to be deployed to production.<\/p>\n\n ",
"format": "full_html",
"processed": "\n <p>I recently made a change to a Drupal project with several custom modules.<\/p>\n\n<p>As part of the change, there was a method that was no longer being used, so I went ahead and removed it.<\/p>\n\n<p>There were no tests for this part of the codebase, and the existing tests were still passing.<\/p>\n\n<p>My change was successfully finished and deployed, including removing the unused method.<\/p>\n\n<p>A few days later, we noticed cron jobs were no longer running on the website.<\/p>\n\n<p>The method I'd removed was attempting to be called from within a different module.<\/p>\n\n<p>Because it no longer existed, it was causing an error and stopping the cron job from running successfully.<\/p>\n\n<p>When I re-added the method, the cron jobs worked again.<\/p>\n\n<p>There were no <code>dependencies<\/code> set in either module's .info.yml file, though that would only prevent you from uninstalling either module.<\/p>\n\n<p>It wouldn't prevent me from deleting code used by another module.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>This is why I've been <a href=\"/daily\/2024\/02\/08\/experimenting-with-architectural-testing\">experimenting with architectural testing<\/a>. To ensure that modules only use their own code and to start enforcing layers within each module.<\/p>\n\n<p>Then, if I had the same situation again, I'd know straight away that there was an issue and not have to wait for the bug to be deployed to production.<\/p>\n\n ",
"processed": "\n <p>I recently made a change to a Drupal project with several custom modules.<\/p>\n\n<p>As part of the change, there was a method that was no longer being used, so I went ahead and removed it.<\/p>\n\n<p>There were no tests for this part of the codebase, and the existing tests were still passing.<\/p>\n\n<p>My change was successfully finished and deployed, including removing the unused method.<\/p>\n\n<p>A few days later, we noticed cron jobs were no longer running on the website.<\/p>\n\n<p>The method I'd removed was attempting to be called from within a different module.<\/p>\n\n<p>Because it no longer existed, it was causing an error and stopping the cron job from running successfully.<\/p>\n\n<p>When I re-added the method, the cron jobs worked again.<\/p>\n\n<p>There were no <code>dependencies<\/code> set in either module's .info.yml file, though that would only prevent you from uninstalling either module.<\/p>\n\n<p>It wouldn't prevent me from deleting code used by another module.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>This is why I've been <a href=\"http:\/\/default\/daily\/2024\/02\/08\/experimenting-with-architectural-testing\">experimenting with architectural testing<\/a>. To ensure that modules only use their own code and to start enforcing layers within each module.<\/p>\n\n<p>Then, if I had the same situation again, I'd know straight away that there was an issue and not have to wait for the bug to be deployed to production.<\/p>\n\n ",
"summary": null
}
],
"feeds_item": [
{
"imported": "1970-01-01T00:33:45+00:00",
"imported": "1970-01-01T00:32:50+00:00",
"guid": null,
"hash": "ac7bcb6f2dcaec78fb9959f65d264b1f",
"target_type": "feeds_feed",