100 lines
No EOL
3.2 KiB
JSON
100 lines
No EOL
3.2 KiB
JSON
{
|
|
"uuid": [
|
|
{
|
|
"value": "13e1b1ea-a0df-43b2-8f1b-e8340bb62df8"
|
|
}
|
|
],
|
|
"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:40+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": "A minor breaking change\n"
|
|
}
|
|
],
|
|
"created": [
|
|
{
|
|
"value": "2023-05-20T00:00:00+00:00"
|
|
}
|
|
],
|
|
"changed": [
|
|
{
|
|
"value": "2025-05-11T09:00:40+00:00"
|
|
}
|
|
],
|
|
"promote": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"sticky": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"default_langcode": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"revision_translation_affected": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"path": [
|
|
{
|
|
"alias": "\/daily\/2023\/05\/20\/a-minor-breaking-change",
|
|
"langcode": "en"
|
|
}
|
|
],
|
|
"body": [
|
|
{
|
|
"value": "\n <p>Today, in the repository of an open-source project, I saw an issue comment saying, \"This is a minor breaking change.\".<\/p>\n\n<p>It detailed what was removed and suggested an alternative.<\/p>\n\n<p>I don't know how you define a \"minor\" breaking change.<\/p>\n\n<p>Is it because it's a single line and easy to replace, or is it part of the code that is rarely used by consumers and less likely to cause an issue?<\/p>\n\n<p>Regardless, if it's a breaking change, anyone using that project will need to update their code if they use something that was removed, whether it's minor or not.<\/p>\n\n ",
|
|
"format": "full_html",
|
|
"processed": "\n <p>Today, in the repository of an open-source project, I saw an issue comment saying, \"This is a minor breaking change.\".<\/p>\n\n<p>It detailed what was removed and suggested an alternative.<\/p>\n\n<p>I don't know how you define a \"minor\" breaking change.<\/p>\n\n<p>Is it because it's a single line and easy to replace, or is it part of the code that is rarely used by consumers and less likely to cause an issue?<\/p>\n\n<p>Regardless, if it's a breaking change, anyone using that project will need to update their code if they use something that was removed, whether it's minor or not.<\/p>\n\n ",
|
|
"summary": null
|
|
}
|
|
],
|
|
"feeds_item": [
|
|
{
|
|
"imported": "1970-01-01T00:33:45+00:00",
|
|
"guid": null,
|
|
"hash": "fec65b7e84bf75434bce2cbc5521ace3",
|
|
"target_type": "feeds_feed",
|
|
"target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
|
|
}
|
|
]
|
|
} |