Move all files to tome/
This commit is contained in:
parent
5675bcfc36
commit
674daab35b
2874 changed files with 0 additions and 0 deletions
65
tome/content/node.f7411fd1-46e2-4056-be8c-89475875f768.yml
Normal file
65
tome/content/node.f7411fd1-46e2-4056-be8c-89475875f768.yml
Normal file
|
@ -0,0 +1,65 @@
|
|||
uuid:
|
||||
- value: f7411fd1-46e2-4056-be8c-89475875f768
|
||||
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:44+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: |
|
||||
Shortening the feedback loop even more
|
||||
created:
|
||||
- value: '2023-04-25T00:00:00+00:00'
|
||||
changed:
|
||||
- value: '2025-05-11T09:00:44+00:00'
|
||||
promote:
|
||||
- value: false
|
||||
sticky:
|
||||
- value: false
|
||||
default_langcode:
|
||||
- value: true
|
||||
revision_translation_affected:
|
||||
- value: true
|
||||
path:
|
||||
- alias: /daily/2023/04/25/shortening-the-feedback-loop-even-more
|
||||
langcode: en
|
||||
body:
|
||||
- value: |
|
||||
<p>Yesterday's email was about shortening the feedback loop of a CI pipeline by running some of the checks like PHPCS and PHPStan locally and dealing with any errors before they get pushed to the code repository.</p>
|
||||
|
||||
<p>What's even better than writing and committing code and then waiting until just before pushing it to test it? Seeing the errors in real-time and being able to fix them immediately.</p>
|
||||
|
||||
<p>In my Neovim setup (I talked about this at the PHP London meetup recently), I have the Intelephense language server configured to add IDE-like features such as code completion, go-to definition, symbol renaming, etc.</p>
|
||||
|
||||
<p>I also have another plugin - <code>null-ls.nvim</code> - that adds errors from command-line tools to Neovim's diagnostics list.</p>
|
||||
|
||||
<p>So, if I try to do something that would cause a PHPStan failure, such as using an unknown variable or missing a return type, I can see that and fix it immediately and not even wait for a Git hook to run.</p>
|
||||
|
||||
|
||||
format: full_html
|
||||
processed: |
|
||||
<p>Yesterday's email was about shortening the feedback loop of a CI pipeline by running some of the checks like PHPCS and PHPStan locally and dealing with any errors before they get pushed to the code repository.</p>
|
||||
|
||||
<p>What's even better than writing and committing code and then waiting until just before pushing it to test it? Seeing the errors in real-time and being able to fix them immediately.</p>
|
||||
|
||||
<p>In my Neovim setup (I talked about this at the PHP London meetup recently), I have the Intelephense language server configured to add IDE-like features such as code completion, go-to definition, symbol renaming, etc.</p>
|
||||
|
||||
<p>I also have another plugin - <code>null-ls.nvim</code> - that adds errors from command-line tools to Neovim's diagnostics list.</p>
|
||||
|
||||
<p>So, if I try to do something that would cause a PHPStan failure, such as using an unknown variable or missing a return type, I can see that and fix it immediately and not even wait for a Git hook to run.</p>
|
||||
|
||||
|
||||
summary: null
|
||||
field_daily_email_cta: { }
|
Loading…
Add table
Add a link
Reference in a new issue