Migrate content to YAML
This commit is contained in:
parent
3d76aa0c3b
commit
9d5a930eab
4550 changed files with 93849 additions and 129734 deletions
65
content/node.2d0b16d8-0781-411e-a06b-f62bf9a9c253.yml
Normal file
65
content/node.2d0b16d8-0781-411e-a06b-f62bf9a9c253.yml
Normal file
|
@ -0,0 +1,65 @@
|
|||
uuid:
|
||||
- value: 2d0b16d8-0781-411e-a06b-f62bf9a9c253
|
||||
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:51+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: |
|
||||
One test a day keeps bugs away
|
||||
created:
|
||||
- value: '2022-11-18T00:00:00+00:00'
|
||||
changed:
|
||||
- value: '2025-05-11T09:00:51+00:00'
|
||||
promote:
|
||||
- value: false
|
||||
sticky:
|
||||
- value: false
|
||||
default_langcode:
|
||||
- value: true
|
||||
revision_translation_affected:
|
||||
- value: true
|
||||
path:
|
||||
- alias: /daily/2022/11/18/one-test-a-day-keeps-bugs-away
|
||||
langcode: en
|
||||
body:
|
||||
- value: |
|
||||
<p>This is a quote from a presentation by Diego Aguiar at SymfonyCon that I saw from <a href="https://twitter.com/SymfonyCasts/status/1593551105471938560?t=A8wnRUa0tLbb2q5qLhcQnA">a tweet from SymfonyCasts</a>.</p>
|
||||
|
||||
<p>I haven't seen the rest of the presentation, but I liked this quote and the idea of continuously improving a codebase using automated tests.</p>
|
||||
|
||||
<p>The talk was titled "Advanced Test Driven Development" so I assume that it was focused on ensuring that new functionality also has accompanying tests but it could also apply to existing code.</p>
|
||||
|
||||
<p>A lot of existing code that I've worked on wasn't covered by tests, so going back and writing tests for that code would be beneficial too - even if it's only one test a day. It would help to prevent and uncover existing bugs, enable the code to be refactored and changed without introducing regressions, and make the codebase more maintainable.</p>
|
||||
|
||||
<p>Small changes over time add up.</p>
|
||||
|
||||
|
||||
format: full_html
|
||||
processed: |
|
||||
<p>This is a quote from a presentation by Diego Aguiar at SymfonyCon that I saw from <a href="https://twitter.com/SymfonyCasts/status/1593551105471938560?t=A8wnRUa0tLbb2q5qLhcQnA">a tweet from SymfonyCasts</a>.</p>
|
||||
|
||||
<p>I haven't seen the rest of the presentation, but I liked this quote and the idea of continuously improving a codebase using automated tests.</p>
|
||||
|
||||
<p>The talk was titled "Advanced Test Driven Development" so I assume that it was focused on ensuring that new functionality also has accompanying tests but it could also apply to existing code.</p>
|
||||
|
||||
<p>A lot of existing code that I've worked on wasn't covered by tests, so going back and writing tests for that code would be beneficial too - even if it's only one test a day. It would help to prevent and uncover existing bugs, enable the code to be refactored and changed without introducing regressions, and make the codebase more maintainable.</p>
|
||||
|
||||
<p>Small changes over time add up.</p>
|
||||
|
||||
|
||||
summary: null
|
||||
field_daily_email_cta: { }
|
Loading…
Add table
Add a link
Reference in a new issue