@Skoop You can actually install phpstan/phpstan with composer as a regular dev dependency, as it effectively just ships a phar bundling its own dependencies.
It's more convenient, and you still get the benefits of the phar approach. Extensions work out of the box.
Yesterday I had to block a specially aggressive and entitled user from my GitHub projects.
A second later he had a new account, so I had to block interactions from all new users as well.
He was very rude, demanded to be helped, and literally told me I was less helpful than ChatGPT.
He created the same issue three times, just to be annoying and noisy.
I honestly don't know how someone can think that's the best way to invest their time.
I'm looking for example repos using ESLint v8 and a .eslintrc, .eslintrc.json, or .eslintrc.yml file to test a config migration tool I'm working on. Please reply with your repo URL.
(I can't promise I'll get to all of them, but trying to get a representative sample.)
Please, web app developers, consider how your users will upgrade. If your upgrade process is "remove the old one, unzip the new one", then it's not an upgrade process. It's an encouragement to never upgrade.
@Crell Do you have some recommendation on how to address that on a self-hosted #php app?
I maintain one which suffers from this and I would like to eventually address it, but I have never found an approach where there's no risk of breaking things without an easy way to roll back.
I provide a CLI tool which helps, but still requires you to manually "download and unzip".
The new #redis website has broken so many links. Some redirect to their new corresponding urls, but not all of them, and it's very hard to find anything in their new marketing-focused website 😩
Life of the Staff Software Engineer — 6 hours over two days of step-debugging a failed test, and going over ALL the tests, and checking my test factories, to discover deep in the code I was using a datetime library wrong.
Apparently some people need to hear this so here we go: doctrine/orm 3 is compatible with doctrine/dbal 3, so it should be possible for you to upgrade to doctrine/orm 3, test and deploy, let things run for a few days and then upgrade to doctrine/dbal 4 instead of upgrading both packages at once. Also, if you use doctrine/orm is mentioned in your composer.json, but not doctrine/dbal, you're probably doing it wrong.
Do I know any software engineers who work at at Chess.com?
LinkedIn says I don’t, but maybe I’m connected to someone here who works there. If so, please DM me. I have some questions about a job posting, and maybe you can help.