From 8ffafc444ca4492ddcb8b7a6550c93e823c154d9 Mon Sep 17 00:00:00 2001 From: Oliver Davies Date: Wed, 26 Apr 2023 16:11:21 +0100 Subject: [PATCH] daily-email: add 2023-04-25 --- src/content/daily-email/2023-04-25.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 src/content/daily-email/2023-04-25.md diff --git a/src/content/daily-email/2023-04-25.md b/src/content/daily-email/2023-04-25.md new file mode 100644 index 00000000..01e8549b --- /dev/null +++ b/src/content/daily-email/2023-04-25.md @@ -0,0 +1,21 @@ +--- +title: > + Shortening the feedback loop even more +pubDate: 2023-04-25 +permalink: > + archive/2023/04/25/shortening-the-feedback-loop-even-more +tags: + - development + - devops + - neovim +--- + +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. + +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. + +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. + +I also have another plugin - `null-ls.nvim` - that adds errors from command-line tools to Neovim's diagnostics list. + +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.