opdavies/oliverdavies.uk
1
0
Fork 0
Code Issues 1 Pull requests Projects 1 Releases Packages Wiki Activity Actions

Remove the feeds module

Browse source
This commit is contained in:
Oliver Davies 2025-05-30 16:19:41 +01:00
parent acfd1cca8d
commit 0c98be96eb
851 changed files with 840 additions and 10348 deletions
Download patch file Download diff file Expand all files Collapse all files

9
content/node.c8d78160-4a98-441c-a707-c1fde53f9044.json
View file

@ -87,14 +87,5 @@
"processed": "\n <p>Over the last few days, I've written about watchers and running commands such as automated tests when files are changed.<\/p>\n\n<p>Some tools have this built in, whilst others don't.<\/p>\n\n<p>I've used different tools to do this and recently switched to <code>entr<\/code>.<\/p>\n\n<p>The previous one wasn't showing me the output from running Drupal automated tests, which <code>entr<\/code> does.<\/p>\n\n<p>I also like that it follows the UNIX philosophy of doing one thing well and working well with other programs.<\/p>\n\n<p>For example, to run my automated tests when I change a file, I need to run <code>find web\/modules\/custom | entr .\/run test<\/code>.<\/p>\n\n<p><code>entr<\/code> isn't concerned with how to find the list of files to watch - only what to do with them.<\/p>\n\n<p>To get the list of files, I use the <code>find<\/code> command and provide the files to <code>entr<\/code>.<\/p>\n\n<p>I also like to do this with my application code. I like to write small modules and libraries with clear boundaries and responsibilities, do their tasks well, and work well with other parts of the application.<\/p>\n\n ",
"summary": null
}
],
"feeds_item": [
{
"imported": "1970-01-01T00:32:50+00:00",
"guid": null,
"hash": "56cd66100b039fcf69f6ebcd06176a9b",
"target_type": "feeds_feed",
"target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
}
]
}