Move all files to tome/
This commit is contained in:
parent
5675bcfc36
commit
674daab35b
2874 changed files with 0 additions and 0 deletions
|
@ -1,68 +0,0 @@
|
|||
uuid:
|
||||
- value: 667d02f9-f672-4a0c-a9cd-e8111ed1d8bd
|
||||
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:18+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: 'You should know when to remove a feature flag'
|
||||
created:
|
||||
- value: '2024-03-12T00:00:00+00:00'
|
||||
changed:
|
||||
- value: '2025-05-11T09:00:18+00:00'
|
||||
promote:
|
||||
- value: false
|
||||
sticky:
|
||||
- value: false
|
||||
default_langcode:
|
||||
- value: true
|
||||
revision_translation_affected:
|
||||
- value: true
|
||||
path:
|
||||
- alias: /daily/2024/03/12/you-should-know-when-to-remove-a-feature-flag
|
||||
langcode: en
|
||||
body:
|
||||
- value: |
|
||||
<p><a href="/daily/2024/03/11/feature-flags-should-be-short-lived">In yesterday's email</a>, I mentioned my recent <a href="https://twitter.com/opdavies/status/1767846980250714261">"minimum viable feature flag" tweet</a> and that I think feature flags should be short-lived.</p>
|
||||
|
||||
<p>But how do you know when a feature flag should be removed?</p>
|
||||
|
||||
<p>My approach is to add a TODO comment above where I use a feature flag.</p>
|
||||
|
||||
<p>In that comment, I added why the feature flag was added and when it can be removed.</p>
|
||||
|
||||
<p>It can be something like "Remove this when x is deployed" and/or a targeted date when I'd expect to be able to remove the flag.</p>
|
||||
|
||||
<p>Then, when reading through the code, anyone can see when it should be possible to remove each feature flag, and it's easy to find flags that can be removed by reviewing the TODO comments.</p>
|
||||
|
||||
|
||||
format: full_html
|
||||
processed: |
|
||||
<p><a href="/daily/2024/03/11/feature-flags-should-be-short-lived">In yesterday's email</a>, I mentioned my recent <a href="https://twitter.com/opdavies/status/1767846980250714261">"minimum viable feature flag" tweet</a> and that I think feature flags should be short-lived.</p>
|
||||
|
||||
<p>But how do you know when a feature flag should be removed?</p>
|
||||
|
||||
<p>My approach is to add a TODO comment above where I use a feature flag.</p>
|
||||
|
||||
<p>In that comment, I added why the feature flag was added and when it can be removed.</p>
|
||||
|
||||
<p>It can be something like "Remove this when x is deployed" and/or a targeted date when I'd expect to be able to remove the flag.</p>
|
||||
|
||||
<p>Then, when reading through the code, anyone can see when it should be possible to remove each feature flag, and it's easy to find flags that can be removed by reviewing the TODO comments.</p>
|
||||
|
||||
|
||||
summary: null
|
||||
field_daily_email_cta: { }
|
Loading…
Add table
Add a link
Reference in a new issue