100 lines
No EOL
4 KiB
JSON
100 lines
No EOL
4 KiB
JSON
{
|
|
"uuid": [
|
|
{
|
|
"value": "a5edab26-6910-43c9-ba33-3f482849596a"
|
|
}
|
|
],
|
|
"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:36+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": "Stick to conventions\n"
|
|
}
|
|
],
|
|
"created": [
|
|
{
|
|
"value": "2023-07-27T00:00:00+00:00"
|
|
}
|
|
],
|
|
"changed": [
|
|
{
|
|
"value": "2025-05-11T09:00:36+00:00"
|
|
}
|
|
],
|
|
"promote": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"sticky": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"default_langcode": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"revision_translation_affected": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"path": [
|
|
{
|
|
"alias": "\/daily\/2023\/07\/27\/stick-to-conventions",
|
|
"langcode": "en"
|
|
}
|
|
],
|
|
"body": [
|
|
{
|
|
"value": "\n <p>If you're performing a task as there's already a convention on how to do it, stick to it.<\/p>\n\n<p>If the codebase follows a particular coding standard, use it.<\/p>\n\n<p>If a project uses repository classes instead of interacting directly with a database, do that with your code too.<\/p>\n\n<p>If you use a framework with a service container and uses dependency injection, do that instead of manually creating classes.<\/p>\n\n<p>If you need additional functionality for a Drupal project and there's an established and well-known module that adds it, use it. Unless it doesn't meet your needs, in which case, document why that's the case and why you used a different module or wrote a custom implementation.<\/p>\n\n<p>If you need to create a content listing page, use the Views module, which is a standard approach. If not, document why and then explore other solutions.<\/p>\n\n<p>If you don't follow a convention, it will be harder for you or others to work on it in the future.<\/p>\n\n ",
|
|
"format": "full_html",
|
|
"processed": "\n <p>If you're performing a task as there's already a convention on how to do it, stick to it.<\/p>\n\n<p>If the codebase follows a particular coding standard, use it.<\/p>\n\n<p>If a project uses repository classes instead of interacting directly with a database, do that with your code too.<\/p>\n\n<p>If you use a framework with a service container and uses dependency injection, do that instead of manually creating classes.<\/p>\n\n<p>If you need additional functionality for a Drupal project and there's an established and well-known module that adds it, use it. Unless it doesn't meet your needs, in which case, document why that's the case and why you used a different module or wrote a custom implementation.<\/p>\n\n<p>If you need to create a content listing page, use the Views module, which is a standard approach. If not, document why and then explore other solutions.<\/p>\n\n<p>If you don't follow a convention, it will be harder for you or others to work on it in the future.<\/p>\n\n ",
|
|
"summary": null
|
|
}
|
|
],
|
|
"feeds_item": [
|
|
{
|
|
"imported": "1970-01-01T00:33:45+00:00",
|
|
"guid": null,
|
|
"hash": "6450282a1b4fe2e23ac91ffacb7cd5c1",
|
|
"target_type": "feeds_feed",
|
|
"target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
|
|
}
|
|
]
|
|
} |