100 lines
No EOL
4.3 KiB
JSON
100 lines
No EOL
4.3 KiB
JSON
{
|
|
"uuid": [
|
|
{
|
|
"value": "72cd14f3-0c15-4b0b-b1c6-328d570f3b01"
|
|
}
|
|
],
|
|
"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:59+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": "Why I use long parameter names in scripts"
|
|
}
|
|
],
|
|
"created": [
|
|
{
|
|
"value": "2024-05-23T00:00:00+00:00"
|
|
}
|
|
],
|
|
"changed": [
|
|
{
|
|
"value": "2025-04-16T14:12:59+00:00"
|
|
}
|
|
],
|
|
"promote": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"sticky": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"default_langcode": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"revision_translation_affected": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"path": [
|
|
{
|
|
"alias": "\/daily\/2024\/05\/23\/why-i-use-long-parameter-names-in-scripts",
|
|
"langcode": "en"
|
|
}
|
|
],
|
|
"body": [
|
|
{
|
|
"value": "\n <p>The other day, <a href=\"http:\/\/localhost:8000\/daily\/2024\/05\/21\/which-commit-has-the-largest-message\">I posted about a script I'd written<\/a> that found the longest commit message in a repository.<\/p>\n\n<p>As I couldn't find a native way to do this with Git, the script loops over each commit in the repository, calculates its length and stores the length and commit SHA in a file.<\/p>\n\n<p>The lines in the file are sorted so the longest commit is first.<\/p>\n\n<p>Whilst I commonly use short parameters, such as <code>git add -p<\/code> when typing commands, in scripts, I prefer to use the equivalent longer parameters, where possible.<\/p>\n\n<p>For example, in the script, I execute this command to sort the lines:<\/p>\n\n<pre><code class=\"bash\">sort \"${result_file}\" --reverse --numeric-sort --output \"${result_file}\"\n<\/code><\/pre>\n\n<p>This could be re-written as:<\/p>\n\n<pre><code class=\"bash\">sort \"${result_file}\" -rn -o \"${result_file}\"\n<\/code><\/pre>\n\n<p>Whilst the original is more verbose and longer to type, I prefer its verbosity which makes it easier for me or others to read and understand in the future.<\/p>\n\n ",
|
|
"format": "full_html",
|
|
"processed": "\n <p>The other day, <a href=\"http:\/\/localhost:8000\/daily\/2024\/05\/21\/which-commit-has-the-largest-message\">I posted about a script I'd written<\/a> that found the longest commit message in a repository.<\/p>\n\n<p>As I couldn't find a native way to do this with Git, the script loops over each commit in the repository, calculates its length and stores the length and commit SHA in a file.<\/p>\n\n<p>The lines in the file are sorted so the longest commit is first.<\/p>\n\n<p>Whilst I commonly use short parameters, such as <code>git add -p<\/code> when typing commands, in scripts, I prefer to use the equivalent longer parameters, where possible.<\/p>\n\n<p>For example, in the script, I execute this command to sort the lines:<\/p>\n\n<pre><code class=\"bash\">sort \"${result_file}\" --reverse --numeric-sort --output \"${result_file}\"\n<\/code><\/pre>\n\n<p>This could be re-written as:<\/p>\n\n<pre><code class=\"bash\">sort \"${result_file}\" -rn -o \"${result_file}\"\n<\/code><\/pre>\n\n<p>Whilst the original is more verbose and longer to type, I prefer its verbosity which makes it easier for me or others to read and understand in the future.<\/p>\n\n ",
|
|
"summary": null
|
|
}
|
|
],
|
|
"feeds_item": [
|
|
{
|
|
"imported": "2025-04-16T14:12:59+00:00",
|
|
"guid": null,
|
|
"hash": "75932acc0c689358346126c8018686f1",
|
|
"target_type": "feeds_feed",
|
|
"target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
|
|
}
|
|
]
|
|
} |