91 lines
No EOL
3.2 KiB
JSON
91 lines
No EOL
3.2 KiB
JSON
{
|
|
"uuid": [
|
|
{
|
|
"value": "4d270194-23a5-445f-8b66-5ee347054400"
|
|
}
|
|
],
|
|
"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": "Should you feature flag everything?\n"
|
|
}
|
|
],
|
|
"created": [
|
|
{
|
|
"value": "2023-06-13T00: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\/06\/13\/should-you-feature-flag-everything",
|
|
"langcode": "en"
|
|
}
|
|
],
|
|
"body": [
|
|
{
|
|
"value": "\n <p>Whilst it's probably impractical to feature flag every new feature or change to your application, considering it is something I do for each change.<\/p>\n\n<p>If you find a bug after a feature has been released, if it's feature flagged, you can quickly disable it without needing to make a code change or release another version.<\/p>\n\n<p>Instead of needing a rollback plan for a release and reverting to the previous version, it can be as simple as disabling the feature flag again to turn it off whilst the cause is investigated.<\/p>\n\n<p>There is a maintenance overhead to adding a feature flag, and it can cause complexity by creating separate paths within the code but using feature flags gives a lot of benefits too.<\/p>\n\n ",
|
|
"format": "full_html",
|
|
"processed": "\n <p>Whilst it's probably impractical to feature flag every new feature or change to your application, considering it is something I do for each change.<\/p>\n\n<p>If you find a bug after a feature has been released, if it's feature flagged, you can quickly disable it without needing to make a code change or release another version.<\/p>\n\n<p>Instead of needing a rollback plan for a release and reverting to the previous version, it can be as simple as disabling the feature flag again to turn it off whilst the cause is investigated.<\/p>\n\n<p>There is a maintenance overhead to adding a feature flag, and it can cause complexity by creating separate paths within the code but using feature flags gives a lot of benefits too.<\/p>\n\n ",
|
|
"summary": null
|
|
}
|
|
]
|
|
} |