91 lines
No EOL
3.4 KiB
JSON
91 lines
No EOL
3.4 KiB
JSON
{
|
|
"uuid": [
|
|
{
|
|
"value": "59ae3523-9dc9-4b61-8387-aaeb708385e6"
|
|
}
|
|
],
|
|
"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:06+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": "Be consistent"
|
|
}
|
|
],
|
|
"created": [
|
|
{
|
|
"value": "2024-09-20T00:00:00+00:00"
|
|
}
|
|
],
|
|
"changed": [
|
|
{
|
|
"value": "2025-05-11T09:00:06+00:00"
|
|
}
|
|
],
|
|
"promote": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"sticky": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"default_langcode": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"revision_translation_affected": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"path": [
|
|
{
|
|
"alias": "\/daily\/2024\/09\/20\/be-consistent",
|
|
"langcode": "en"
|
|
}
|
|
],
|
|
"body": [
|
|
{
|
|
"value": "\n <p>Whether you <a href=\"\/daily\/2024\/09\/19\/the-two-ways-of-writing-php-code\">prefer strict code or not<\/a>, <a href=\"\/daily\/2023\/04\/19\/camel-case-or-snake-case-for-drupal-code\">use snake-case or camel-case for variable names<\/a> or <a href=\"\/daily\/2022\/11\/14\/camel-case-or-snake-case-for-test-methods\">how you write your test methods<\/a>, it is important to be consistent in how code is written.<\/p>\n\n<p>If you're working in a file that uses snake-case variable names, you should do the same and follow the same conventions.<\/p>\n\n<p>When reading a file, everything should be consistent and seem like it was written by the same person following the same approaches.<\/p>\n\n<p>Otherwise, when you need to add to or refactor this code in the future, it will be harder to do so.<\/p>\n\n<p>Consistency is key.<\/p>\n\n ",
|
|
"format": "full_html",
|
|
"processed": "\n <p>Whether you <a href=\"http:\/\/default\/daily\/2024\/09\/19\/the-two-ways-of-writing-php-code\">prefer strict code or not<\/a>, <a href=\"http:\/\/default\/daily\/2023\/04\/19\/camel-case-or-snake-case-for-drupal-code\">use snake-case or camel-case for variable names<\/a> or <a href=\"http:\/\/default\/daily\/2022\/11\/14\/camel-case-or-snake-case-for-test-methods\">how you write your test methods<\/a>, it is important to be consistent in how code is written.<\/p>\n\n<p>If you're working in a file that uses snake-case variable names, you should do the same and follow the same conventions.<\/p>\n\n<p>When reading a file, everything should be consistent and seem like it was written by the same person following the same approaches.<\/p>\n\n<p>Otherwise, when you need to add to or refactor this code in the future, it will be harder to do so.<\/p>\n\n<p>Consistency is key.<\/p>\n\n ",
|
|
"summary": null
|
|
}
|
|
]
|
|
} |