91 lines
No EOL
3.6 KiB
JSON
91 lines
No EOL
3.6 KiB
JSON
{
|
|
"uuid": [
|
|
{
|
|
"value": "b16f4c7f-2876-4165-8c38-a7ef0b9cbb13"
|
|
}
|
|
],
|
|
"langcode": [
|
|
{
|
|
"value": "en"
|
|
}
|
|
],
|
|
"type": [
|
|
{
|
|
"target_id": "daily_email",
|
|
"target_type": "node_type",
|
|
"target_uuid": "8bde1f2f-eef9-4f2d-ae9c-96921f8193d7"
|
|
}
|
|
],
|
|
"revision_timestamp": [
|
|
{
|
|
"value": "2025-05-11T09:00:16+00: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": "What about updating custom modules and themes?"
|
|
}
|
|
],
|
|
"created": [
|
|
{
|
|
"value": "2024-04-14T00:00:00+00:00"
|
|
}
|
|
],
|
|
"changed": [
|
|
{
|
|
"value": "2025-05-11T09:00:16+00:00"
|
|
}
|
|
],
|
|
"promote": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"sticky": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"default_langcode": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"revision_translation_affected": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"path": [
|
|
{
|
|
"alias": "\/daily\/2024\/04\/14\/what-about-updating-custom-modules-and-themes",
|
|
"langcode": "en"
|
|
}
|
|
],
|
|
"body": [
|
|
{
|
|
"value": "\n <p><a href=\"\/daily\/2024\/04\/12\/drupal-rector-and-the-project-update-bot\">Yesterday's email<\/a> was about using Drupal Rector and the Automated Project Update bot to update contributed modules.<\/p>\n\n<p>But what about custom modules within your application?<\/p>\n\n<p>To do this, I use the <code>drupal-check<\/code> tool, which is built on PHPStan, and the Upgrade Status module.<\/p>\n\n<p>They scan your custom modules and themes and report any deprecated code within your custom projects - i.e. code that will be removed in a future major version - and tell you what new code to use instead.<\/p>\n\n<p>Once you've removed any deprecations, your module or theme will be ready for the next major version of Drupal.<\/p>\n\n<p>This is the approach I've used to upgrade numerous websites between major modern versions of Drupal, making small updates to existing code instead of having to rewrite it from scratch.<\/p>\n\n ",
|
|
"format": "full_html",
|
|
"processed": "\n <p><a href=\"http:\/\/default\/daily\/2024\/04\/12\/drupal-rector-and-the-project-update-bot\">Yesterday's email<\/a> was about using Drupal Rector and the Automated Project Update bot to update contributed modules.<\/p>\n\n<p>But what about custom modules within your application?<\/p>\n\n<p>To do this, I use the <code>drupal-check<\/code> tool, which is built on PHPStan, and the Upgrade Status module.<\/p>\n\n<p>They scan your custom modules and themes and report any deprecated code within your custom projects - i.e. code that will be removed in a future major version - and tell you what new code to use instead.<\/p>\n\n<p>Once you've removed any deprecations, your module or theme will be ready for the next major version of Drupal.<\/p>\n\n<p>This is the approach I've used to upgrade numerous websites between major modern versions of Drupal, making small updates to existing code instead of having to rewrite it from scratch.<\/p>\n\n ",
|
|
"summary": null
|
|
}
|
|
]
|
|
} |