@Skoop The problem is that PHStan for no apparent reason prefixes (using phpscoper) all the classes in the phar thus having no means to have an extension find the relevant classes.
Is it just me or is #phpstorm getting worse by the day?
I'm runnig 2024.1 (Build #PS-241.14494.237, built on March 27, 2024) but have to constantly restart the IDE to fix bizarre errors like PHPStorm claiming a property or parameter isn't used while highlighting the very use a line later, inconsistently resolving asserts with instanceof checks - e.g. claiming a method doesn't exist in the class referenced in a different assert and not seeing a parameter that is clearly there... #fail#ensh11n
Is it just me or is anyone else running their own mailserver experiencing a lot servers being blocked by zen.spamhaus.org currently that one would assume not to be considered offensive?
This looks suspiciously similar to azjezz/psl, just with a different API. It even has the same name: PHP Standard Library.
The PHP community would be better if devs worked together instead of copying and re-branding someone else's work. Credit to azjezz for the original PSL.
@afilina At least the screenshot shows a perfect example of adding pointless complexity rather than addressing the design flaw of using implicit APIs with magic strings.
@Crell The thing that I see happening a lot is that things are made configurable that aren't actually configurable - for instance because there's only one implementation to choose from - or should be represented by code rather then being generalized into something requiring more configuration than actual code would have...
PHPStan reports "Property stdClassList::$classes (array<int, stdClass>) does not accept array<int|string, stdClass>." but I would expect that $classes will always be array<int, stdClass> without any string-keys
@shochdoerfer@heiglandreas@phpstan The variadic doesn't care. All phpstan is telling you that if you do new StdClassList( ...['a' => new StdClass]); the key "a" is kept in the params array. And does not magically turn into an int. If you'd do $this->classes = array_values($classes); the problem is gone.
I finally started the project to write a small purpose-driven FTP server that accepts a file and sends it to an email address.
I decided to use ReactPHP for that.
FTP is.... challenging. On the server side at least.
Why? I have a scanner that can scan to FTP. But I need to send the files via email. And the FTP server I so far used can't send emails from new files. So what's the natural approach as developer?
