From 88d5d58cf04a3107260ad467e5b7abc660d60dbe Mon Sep 17 00:00:00 2001
From: Oliver Davies <oliver@oliverdavies.dev>
Date: Tue, 16 Apr 2024 00:25:40 +0100
Subject: [PATCH] Add daily email for 2024-04-13
Rector is not just for Drupal
---
source/_daily_emails/2024-04-13.md | 28 ++++++++++++++++++++++++++++
1 file changed, 28 insertions(+)
create mode 100644 source/_daily_emails/2024-04-13.md
diff --git a/source/_daily_emails/2024-04-13.md b/source/_daily_emails/2024-04-13.md
new file mode 100644
index 00000000..9c6f8f0e
--- /dev/null
+++ b/source/_daily_emails/2024-04-13.md
@@ -0,0 +1,28 @@
+---
+title: Rector is not just for Drupal
+date: 2024-04-13
+permalink: archive/2024/04/13/rector-is-not-just-for-drupal
+tags:
+ - software-development
+ - drupal
+ - php
+cta: ~
+snippet: |
+ Why spend time doing manual tasks that can be automated? Instead, save time by using tools like Rector.
+---
+
+I like framework-agnostic tools.
+
+I like to reuse knowledge and tools across projects, whether I'm working with Drupal, Symfony, Laravel or Sculpin.
+
+Rector is one of those tools.
+
+[Yesterday] I said I use it to create automatic updates to my Drupal module code, but it can be used for other PHP projects, too.
+
+If you're upgrading a PHP library and want to use promoted constructor properties, for example, Rector can do that for you - and a lot more.
+
+You define which rules or presets you want to use, run Rector on the code, and it will make those changes.
+
+Having Rector do this work leaves me free to stay focused on other tasks.
+
+[yesterday]: {{site.url}}/archive/2024/04/12/drupal-rector-and-the-project-update-bot