oliverdavies.uk/content/node.4e0d5cba-13d4-497e-a320-d1236df4dce2.json

91 lines
4.7 KiB
JSON
Raw Normal View History

2025-05-11 07:15:45 +01:00
{
"uuid": [
{
2025-05-11 09:40:11 +01:00
"value": "4e0d5cba-13d4-497e-a320-d1236df4dce2"
2025-05-11 07:15:45 +01:00
}
],
"langcode": [
{
"value": "en"
}
],
"type": [
{
"target_id": "daily_email",
"target_type": "node_type",
"target_uuid": "8bde1f2f-eef9-4f2d-ae9c-96921f8193d7"
}
],
"revision_timestamp": [
{
2025-05-11 09:40:11 +01:00
"value": "2025-05-11T09:00:20+00:00"
2025-05-11 07:15:45 +01:00
}
],
"revision_uid": [
{
"target_type": "user",
"target_uuid": "b8966985-d4b2-42a7-a319-2e94ccfbb849"
}
],
"revision_log": [],
"status": [
{
"value": true
}
],
"uid": [
{
"target_type": "user",
"target_uuid": "b8966985-d4b2-42a7-a319-2e94ccfbb849"
}
],
"title": [
{
"value": "Defining boundaries between custom Drupal modules"
}
],
"created": [
{
"value": "2024-02-09T00:00:00+00:00"
}
],
"changed": [
{
2025-05-11 09:40:11 +01:00
"value": "2025-05-11T09:00:20+00:00"
2025-05-11 07:15:45 +01:00
}
],
"promote": [
{
"value": false
}
],
"sticky": [
{
"value": false
}
],
"default_langcode": [
{
"value": true
}
],
"revision_translation_affected": [
{
"value": true
}
],
"path": [
{
"alias": "\/daily\/2024\/02\/09\/defining-boundaries-between-custom-drupal-modules",
"langcode": "en"
}
],
"body": [
{
2025-05-30 02:14:32 +01:00
"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 ",
2025-05-11 07:15:45 +01:00
"format": "full_html",
2025-05-30 02:14:32 +01:00
"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 ",
2025-05-11 07:15:45 +01:00
"summary": null
}
]
}