Spent the morning writing code to test a microservices architecture. Wondering at what point testing relationships between services becomes cumbersome.
@sarah I was discussing contract testing w/ colleagues yesterday, which is exactly what you're talking about.
IMHO, you either go full-decoupled, and leverage stuff like OpenAPI to do contract testing in isolation, or you go full-coordination, and prop up choreography testing and enforce cross-referenced testing with some tooling like Pact and the like.
You pick your poison, but IMHO the middle ground is counterproductive, you don't get a clear architecture or a good collaboration environment
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.
I wrote that, and it totally revolves around variance, since I had to devise a way around that to create a smooth migration path for PHP-FIG new typed interfaces...
@ollieread well, the PSR scope is intentionally reduced to avoid over-standardization. And those are actively being used by multiple current frameworks and libraries right now.
Still, there are a couple of cases where we would like to do improvements, and the service registration for container is one currently being discussed in the mailing list.
ok #php folks, you were right Rector is pretty cool. The learning curve is steep AF, and the docs are, well, let's just say they're written by engineers for engineers. But given the target audience for this tool, that's OK. I've not yet done the changes I was originally asking about with it, because the config for it is going to be a PITA to build. I've been starting small. But what I've done so far has been pretty cool! I've done some wild things with RenameClassConstFetchRector for example. 🧵
@dragonmantank if you transfer between Samsung, you basically don't have to re-log into anything, they have a dedicated app to transfer everything, even directly via an USB C cable between the two phones..
Otherwise, I've found that having a password manager reduces a lot the login friction, whenever a "login via Google SSO" is not available.
I have found myself, for the first time, having to write what I consider worse code to satisfy Psalm static analysis. Here's a watered-down example showing what I consider odd behavior.
@sidawson@cspray that's not the issue here. The same snippet should trigger PHPStan errors too, because it was the starting definition too strict, since it requires "list".
List is an array with only consecutive integer keys. If you don't re-index (and the spread operator does) you don't have a (guaranteed) list anymore.
Proposal for a conference talk: How to configure #PHPStorm and all its tooling extensions (xdebug, phpstan, php-cs-fixer, etc.) to use a docker container consistently.