For those #php people that are using continuous integration for unit testing, static analysis and the likes, would you consider using a service that you feed test results for nice reports and analysis? (also includes composer.lock analysis and stuff)
@ollieread think i tend to build everything as a multiton even if its intended to be a singleton.
mostly because if think i wanted a singleton the reality is i wanted a single managed instance for the common use case, not so much a device that can literally only burn itself once. which leads me to mostly writing something like this:
So, I’m building a #php dependency-injection package, and it’s a lot of fun. I’ve gone a route that I don’t really see many, if any, following. I suspect it may be that a lot of the solutions out there are old, and while they have been updated, they’re still going to inherit certain approaches.
I need to remember that Mastodon exists! I’m currently writing a bunch of content to do with PHP and this would be the perfect place to talk about that.
I’m currently trying to decide whether #php#reflection is an interesting enough topic that people may like an in-depth course/series on it. It seems to be something a lot of people are vaguely aware of, but don’t really know the details.