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

Make all links relative

Browse source 
Now the abs_to_rel module is enabled, links can be made relative so they
work on the current environment.
This commit is contained in:
Oliver Davies 2025-05-29 16:42:25 +01:00
parent 0d359f81d6
commit 7a7dc297ca
349 changed files with 698 additions and 698 deletions
Download patch file Download diff file Expand all files Collapse all files

4
content/node.b3d2cc06-7cbf-476e-9dc7-fa13ed17363f.json
View file

@ -82,9 +82,9 @@
],
"body": [
{
"value": "\n <p>If you're trying to <a href=\"https:\/\/www.oliverdavies.uk\/daily\/2024\/09\/20\/be-consistent\">keep your code consistent<\/a>, such as following the same coding style or following conventions such as <a href=\"https:\/\/www.oliverdavies.uk\/daily\/2024\/09\/05\/find-vs-get\">find vs get<\/a> or design systems such as repositories or builder classes, instead of relying on manual code review and taking the time of a colleague, you can leverage automation to run checks for you.<\/p>\n\n<p>You can run tools such as phpcs or eslint to enforce a coding style and use Git hooks or a CI pipeline to run them automatically or integrate them into your text editor or IDE so you can see and resolve issues as the code is being written.<\/p>\n\n<p>You can use static analysis tools such as PHPStan to find potential bugs but also enforce conventions by <a href=\"https:\/\/www.oliverdavies.uk\/daily\/2024\/09\/22\/writing-custom-phpstan-rules-for-drupal-projects\">writing custom rules for your project<\/a> or using architectural testing tools such as PHPat.<\/p>\n\n<p>By automating checks, you'll have a consistent result every time and don't need to wait for someone else to find small issues you could have fixed quickly.<\/p>\n\n ",
"value": "\n <p>If you're trying to <a href=\"/daily\/2024\/09\/20\/be-consistent\">keep your code consistent<\/a>, such as following the same coding style or following conventions such as <a href=\"/daily\/2024\/09\/05\/find-vs-get\">find vs get<\/a> or design systems such as repositories or builder classes, instead of relying on manual code review and taking the time of a colleague, you can leverage automation to run checks for you.<\/p>\n\n<p>You can run tools such as phpcs or eslint to enforce a coding style and use Git hooks or a CI pipeline to run them automatically or integrate them into your text editor or IDE so you can see and resolve issues as the code is being written.<\/p>\n\n<p>You can use static analysis tools such as PHPStan to find potential bugs but also enforce conventions by <a href=\"/daily\/2024\/09\/22\/writing-custom-phpstan-rules-for-drupal-projects\">writing custom rules for your project<\/a> or using architectural testing tools such as PHPat.<\/p>\n\n<p>By automating checks, you'll have a consistent result every time and don't need to wait for someone else to find small issues you could have fixed quickly.<\/p>\n\n ",
"format": "full_html",
"processed": "\n <p>If you're trying to <a href=\"https:\/\/www.oliverdavies.uk\/daily\/2024\/09\/20\/be-consistent\">keep your code consistent<\/a>, such as following the same coding style or following conventions such as <a href=\"https:\/\/www.oliverdavies.uk\/daily\/2024\/09\/05\/find-vs-get\">find vs get<\/a> or design systems such as repositories or builder classes, instead of relying on manual code review and taking the time of a colleague, you can leverage automation to run checks for you.<\/p>\n\n<p>You can run tools such as phpcs or eslint to enforce a coding style and use Git hooks or a CI pipeline to run them automatically or integrate them into your text editor or IDE so you can see and resolve issues as the code is being written.<\/p>\n\n<p>You can use static analysis tools such as PHPStan to find potential bugs but also enforce conventions by <a href=\"https:\/\/www.oliverdavies.uk\/daily\/2024\/09\/22\/writing-custom-phpstan-rules-for-drupal-projects\">writing custom rules for your project<\/a> or using architectural testing tools such as PHPat.<\/p>\n\n<p>By automating checks, you'll have a consistent result every time and don't need to wait for someone else to find small issues you could have fixed quickly.<\/p>\n\n ",
"processed": "\n <p>If you're trying to <a href=\"/daily\/2024\/09\/20\/be-consistent\">keep your code consistent<\/a>, such as following the same coding style or following conventions such as <a href=\"/daily\/2024\/09\/05\/find-vs-get\">find vs get<\/a> or design systems such as repositories or builder classes, instead of relying on manual code review and taking the time of a colleague, you can leverage automation to run checks for you.<\/p>\n\n<p>You can run tools such as phpcs or eslint to enforce a coding style and use Git hooks or a CI pipeline to run them automatically or integrate them into your text editor or IDE so you can see and resolve issues as the code is being written.<\/p>\n\n<p>You can use static analysis tools such as PHPStan to find potential bugs but also enforce conventions by <a href=\"/daily\/2024\/09\/22\/writing-custom-phpstan-rules-for-drupal-projects\">writing custom rules for your project<\/a> or using architectural testing tools such as PHPat.<\/p>\n\n<p>By automating checks, you'll have a consistent result every time and don't need to wait for someone else to find small issues you could have fixed quickly.<\/p>\n\n ",
"summary": null
}
],