@voku The Week in Review, Edition 90 (2025-18)

Topics:

🚵‍♂️ Gravel tour to the highest “mountain” in the area

🗺️ Extract extensive data from OpenStreetMap that isn't visible on the map

🖥️ The PHPDoc Guide (2025 Edition)

🗺️ The better-osm-org userscript for deep dives into the OpenStreetMap database

🔦 Prepare for emergencies – useful lists from the Federal Office of Civil Protection and Disaster Assistance

🔊 Listened to this week: Friction, Charlie Tee, Stahler

#Weekly #Gravel #OpenStreetMap #Bikerouter #Golmberg #Brandenburg #Psalm #phpstan #PHPDoc #BetterOSM #Apple #iMessage #Emergency #Stockpile #Obsidian #Techno

https://www.marcusjaschen.de/en/blog/2025/2025-18/

Wochenrückblick, Ausgabe 90 (2025-18)

Themen:

🚵‍♂️ Graveltour zum höchsten Berg in der Umgebung

🗺️ OpenStreetMap umfangreiche Daten entlocken, die auf der Karte nicht zu sehen sind

🖥️ The PHPDoc Guide (2025 Edition) von @voku

🗺️ Das better-osm-org Userscript für Deep Dives in die OpenStreetMap-Datenbank

🔦 Für den Notfall vorsorgen – nützliche Listen vom Bundesamt für Bevölkerungsschutz und Katastrophenhilfe

🔊 In dieser Woche gehört: Friction, Charlie Tee, Stahler

#Wochenrückblick #Gravel #OpenStreetMap #Bikerouter #Golmberg #Brandenburg #Psalm #phpstan #PHPDoc #BetterOSM #Apple #iMessage #Notfall #Vorrat #Obsidian #Techno

https://www.marcusjaschen.de/blog/2025/2025-18/

a #cheatsheet for #PHPStan #Psalm #PHPDoc would be neat. similar as this one for #TypeScript

https://jasondavis.net/@jason/114269720824635092

Sitting in PhpStorm and trying to get type hinting to work for calling generic functions.
I assume `$result` should get the type `T` and `$x` should be parsed as `int`, but the editor gives me no hint at all.
Is this even supposed to work?
```
/**
* @template T
* @param callable(): T $fun
* @return T
*/
function call(callable $fun) {
$result = $fun();
return $result;
}

$x = call(fn() => 1);
```
https://phpstan.org/r/76b4d50f-dd91-4e39-993a-458b26c321cf
#php #phpStorm #generics #phpDoc

Feb 18 08:36:18 lukas: Dear Logbook, I have to write phpdoc's again in 2025 because the PHP LSP market has only intelephense as the only real LS to offer and it is as powerful as my 90 year old grandma. Not even PHP has its own LS. Sad. Here's to a new day of phpdoc's! Logbook over.

#PHP #PHPDoc #LSP #LanguageServer #nvim

Записки разработчика: как подружить D7 свойства и IDE

Приветствую всех неравнодушных! В статье я расскажу, как мы смогли подружить сложные D7 свойства инфоблоков с нашей IDE. Есть в одном проекте такая волшебная штука, как подборы. В них столько свойств, что обычный getList() по 30 записям съедает 6 Гб оперативной памяти, а для оптимизации этого монстра приходится использовать ядро D7. Что же может нам рассказать интернет о том, как правильно обращаться к свойствам инфоблоков, чтобы проект не "ушел отдыхать", обидевшись на всех? 1. Изучим концепцию Нам, как во многих фреймворках, предлагают описать нашу сущность, создать модель и по ней уже баловаться, как пожелаем. Но в нашей сущности получается 570 полей. Одно описание этих полей займет о-о-ой как много времени — не наш вариант.

https://habr.com/ru/articles/865982/

#bitrix #d7 #properties #ide #phpdoc

🚀 PHPStan 2.0 Released: Enhanced Analysis and New Features 🐘

After three years of development, #PHPStan 2.0 is now available, introducing over 180 improvements to #StaticAnalysis for #PHP developers.

Highlights:

🔟 Level 10 Analysis

Provides stricter checks by treating all mixed types strictly.
Helps catch more potential issues in your #Codebase by enforcing stricter #TypeSafety.
📋 List Type Support

Introduces the list type for arrays with sequential integer keys starting at 0.
Enhances #TypeSafety and clarity when working with lists in #PHP.
⚡ Lower Memory Consumption

Optimizations reduce memory usage by 50–70%.
Leads to faster #Performance and less strain on your system during analysis.
✅ Validation of Inline @var Tags

#PHPStan now validates inline @var #PHPDoc tags against the native type of the assigned expression.
Helps maintain accurate type annotations and catch inconsistencies, improving #CodeQuality.
🧹 Reduced Caching and Disk Space Cleanup

Less reliance on caching without sacrificing performance.
Frees up disk space by cleaning up old cache items, aiding in #DiskSpaceManagement.
For a detailed list of changes and a step-by-step upgrade guide, read the full release notes.

Read more: https://phpstan.org/blog/phpstan-2-0-released-level-10-elephpants

Just tried to use `@uses` from #phpdoc in a test to help PHPStorm see a data provider and it immediately clashed with the same one of #phpunit. Didn't know that

We just released #phpdoc v3.5.3. this version contains a number of small bug fixes in our template. And solves an issue with images in guides.

Also added in this version, automated hiding of empty namespaces. They will no longer be visible in the menu.

The new docker image and phar are now available.

https://github.com/phpDocumentor/phpDocumentor/releases/tag/v3.5.3

@typo3 core api documentation is now rendered using #phpDoc we are very pleased to have them on board using our tool.
We will keep helping them to improve the api docs and integrate them better into the rest of the documentation.

Congratulations🥳

https://api.typo3.org/main/

@Jfillian #PHPDoc is your friend

Recently I've seen a lot of people in the #JavaScript community advocating for #JSDoc as a "replacement" of some sort for #TypeScript. As an outsider (even tho I work with #NodeJS full-time now) I cannot shake the feeling of déjà vu.

Before #PHP 7 most developers used #PHPDoc to document input and output too, and though it was better than nothing, it was ugly (IMO) and ultimately impractical.

The solution is right there, I bet some can even smell it...

https://www.youtube.com/watch?v=5ChkQKUzDCs

I have a thought to validate with you related to #php #phpdoc and #exceptions. Having them all documented with `@throws` is generally nice, but is it useful? Do we document all of them or do we treat them like Java's checked exceptions - only document if someone needs to handle that? In custom code the question is a bit redundant, but in frameworks usually there is a fat system that cares about most issues around, so writing all "thows" around the stack might look like an overkill.

After two years of development, we are removing the feature flag for guides. The next release of #phpdoc will come with an out of the box ReStructuredText format.

Allowing you to write end-user documentation next to you api docs.

#php

I know this sounds very meta, but I do absolutely love the way @phpdoc is helping me to write documentation for the #phpdoc libraries. The addition of #restructuredtext support really helps me.

Over a few days I am working on getting #phpstan faster for big union #phpdoc types.

2 PullRequests landed (#2843, #2851) which should improve performance for these edge cases by ~10% and another ~25% 🚀

e.g. #propelorm based projects seem to benefit from it.

Really liking the #PHPUnit 10 attributes. I'm not sure it makes a substantive difference for me in most of my testing, but the vibes are right.

I hope I live to see the day that I can write a #PHP application without using a single #PHPDoc.

I'm planning to add return types to interface methods in a #PHP library. Because of #BC I plan to do this in a next major release.

What's the best practice to document this return type change now, so the users of the library can add the return types now instead of waiting for the major release? Is there a recommended #phpdoc annotation? Or should I use the ReturnTypeWillChange attribute?

#software #dev #Symfony #WebDev

What do you do on your trip home from #symfonycon. Writing code ofcourse! Still 2 hours in the train. Let's see where we can get.
#phpdoc #php

> 「PSR-5全然実装されてない
> しだめだろ」みたいな論調で
> 書こうと思ってたのですが、
> 調べてみたらPhpStorm以外で
> は結構実装されちゃってる感
> じでした

​:qiita:​『2018年のPHPDoc事情とPSR-5』by @tadsan https://qiita.com/tadsan/items/72b02339d12120ca37d7

#PSR5 #PHPDoc #PHPGuru #PHP