100 lines
No EOL
3.6 KiB
JSON
100 lines
No EOL
3.6 KiB
JSON
{
|
|
"uuid": [
|
|
{
|
|
"value": "40de366b-ca47-4ba0-a81b-c8bf0e801d6e"
|
|
}
|
|
],
|
|
"langcode": [
|
|
{
|
|
"value": "en"
|
|
}
|
|
],
|
|
"type": [
|
|
{
|
|
"target_id": "daily_email",
|
|
"target_type": "node_type",
|
|
"target_uuid": "8bde1f2f-eef9-4f2d-ae9c-96921f8193d7"
|
|
}
|
|
],
|
|
"revision_timestamp": [
|
|
{
|
|
"value": "2025-04-16T14:12:58+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 are err, req and res?"
|
|
}
|
|
],
|
|
"created": [
|
|
{
|
|
"value": "2024-08-16T00:00:00+00:00"
|
|
}
|
|
],
|
|
"changed": [
|
|
{
|
|
"value": "2025-04-16T14:12:58+00:00"
|
|
}
|
|
],
|
|
"promote": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"sticky": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"default_langcode": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"revision_translation_affected": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"path": [
|
|
{
|
|
"alias": "\/daily\/2024\/08\/16\/what-are-err--req-and-res",
|
|
"langcode": "en"
|
|
}
|
|
],
|
|
"body": [
|
|
{
|
|
"value": "\n <p>Today, I was at another School of Code hackathon event, mentoring a team of three Developers as they planned and built an application within a day.<\/p>\n\n<p>During the day, we looked at some example documentation that included variable names like <code>err<\/code>, <code>req<\/code>, and <code>res<\/code>.<\/p>\n\n<p>I don't like short variable names like this.<\/p>\n\n<p>I'd suggest calling them what they are - <code>error<\/code>, <code>request<\/code> and <code>response<\/code>.<\/p>\n\n<p>This makes the code clearer and easier to read and understand, particularly if you aren't using types and need additional context.<\/p>\n\n<p>Readability is important as <a href=\"http:\/\/localhost:8000\/daily\/2024\/08\/07\/people-read-more-code-than-they-write\">people read more code than they write<\/a>.<\/p>\n\n ",
|
|
"format": "full_html",
|
|
"processed": "\n <p>Today, I was at another School of Code hackathon event, mentoring a team of three Developers as they planned and built an application within a day.<\/p>\n\n<p>During the day, we looked at some example documentation that included variable names like <code>err<\/code>, <code>req<\/code>, and <code>res<\/code>.<\/p>\n\n<p>I don't like short variable names like this.<\/p>\n\n<p>I'd suggest calling them what they are - <code>error<\/code>, <code>request<\/code> and <code>response<\/code>.<\/p>\n\n<p>This makes the code clearer and easier to read and understand, particularly if you aren't using types and need additional context.<\/p>\n\n<p>Readability is important as <a href=\"http:\/\/localhost:8000\/daily\/2024\/08\/07\/people-read-more-code-than-they-write\">people read more code than they write<\/a>.<\/p>\n\n ",
|
|
"summary": null
|
|
}
|
|
],
|
|
"feeds_item": [
|
|
{
|
|
"imported": "2025-04-16T14:12:58+00:00",
|
|
"guid": null,
|
|
"hash": "c23fb1203fee72bdb3258fe1a8d8cc16",
|
|
"target_type": "feeds_feed",
|
|
"target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
|
|
}
|
|
]
|
|
} |