Tobias Grasse

Endpoint tests to make sure all routes return the expected response. (Relatively) fast and act as a canary: If the endpoint fails, then Inertia/Vue will have a hard time as well. Dusk for the critical paths, but looking forward to Pest browser tests. Ditching Selenium alone should be worth it 😄

"Chatkontrolle" - EU-Staaten erzielen keine Einigung Die EU-Staaten haben erneut keine Einigung auf eine sogenannte Chatkontrolle im Kampf gegen sexualisierte Gewalt gegen Kinder erzielt.

Seems like you don't need to waste paper – at least for now: www.deutschlandfunk.de/eu-staaten-e... (www.tagesschau.de/inland/chatk... was still tentative)

None that I know of, sorry. Tools like LibreOffice have merge mail functions – address field placeholders that are autofilled from a spreadsheet, database, address book etc. I’d target the letters to a few selected representatives, adding a personal line each time. Probably more impact.

A pragmatic guide to modern CSS colours - part one Whether you've got a firm grasp on modern CSS colour capabilities, or you're thinking 'I struggle to understand why I should use modern CSS colours at all', then the first part of this article series,...

Are you the type of dev who just copies and pastes hex codes?

If so, I've written an article over at @piccalil.li just for you!

I take a look at some of the new CSS colour features that are most useful for those who don't really care about colours.

piccalil.li/blog/a-pragm...

Understandable. Honestly, printing your email as-is should suffice. Doesn’t matter if the tone is not 100% formal, many *native* speakers struggle with this. Physical form attracts attention, then your argument is what counts.

Thank you for paying attention to this matter 🙏

Write physical letters. Call their offices by phone.
Emails to state- (MdL) or federal-level (MdB) representative often receive canned responses if any at all. This may be part lack of interest, definitely part sheer volume.

A letter or phone call shows dedication … and cannot be easily ignored.

Yes, to improve static analysis for fellow developers who are not (yet) using your plugin 🙂 I assume docblocks are also a tad more performant?

Thanks for the explainer! Seems best to have basic annotations in the model class while retaining advanced understanding from external helper code.

@laravel-idea.com Can the plugin write PhpDoc annotations in the model file *instead of* helper files like barryvdh/laravel-ide-helper does? Didn't find an option. What is “more powerful” [1] in the plugin version?

1: laravel-idea.com/docs/eloquen...

Absolutely. I feel the same with German public-service offerings (ad-free) vs. anything private … or even ad-supported paid tiers of any streaming service.

But people here complain about “Zwangsgebühren” … [Germany has a mandatory service fee for public-service broadcasting much like the UK]

Sure, done ✅

Super useful!
And yes, absolutely (to both other questions 😄)

Only once its reliably cross-browser though.

Super useful and yes, absolutely.

Only once its cross-browser though.

A screenshot of a macOS terminal, showing the output of a PHP interactive shell which echoes the PHP version ID constant, and a second command that shows the output of PHP – – version

www.php.net/manual/en/re...

Christoph’s screenshot shows a check if the PHP version is below 8.0.0
Basically saves you from parsing a semantic version string into major minor patch.

Similar to migrations: Store the last successful step, and a subsequent run resumes from there. Although this might not be needed if all setup commands are idempotent – like migrations 🙈
My initial hunch was that there might be commands requiring reversal/skipping before setup can run again.

Looks really useful! Onboarding new developers or even just for the occasional clean reinstall. 👏

Do you (plan to) support cancelling/resuming the setup process as well? If, for example, the user aborts the setup after a failed check instead of retrying.

Screenshot of FAQs on nativephp.com discussing their open source and pricing strategies.

They address this in their FAQ: nativephp.com/mobile#:~:te...

Looks intriguing. Would you mind sharing some details? What’s required to make this work, or is this a prototype?

Code snippet demonstrating a potential issue with the discussed approach of asserting inside the Queue::assertPushed callback.

Great one, thank you! Just a tiny pitfall (if I'm not mistaken) in case your Queue fake contains multiple jobs and you want to check if one of them passes the callback: `expect` will throw and thus abort the loop, whereas returning `false` continues with the next job instance. Sample code below.

Yes, at least in endpoint tests I’d still use named routes. Also useful in all contexts where I’m not on the frontend, e.g. links in Mailables.

I find myself repeatedly using @spatie.be ‘s Laravel Media Library, Browsershot, laravel-pdf or laravel-data packages. But I also rarely include them from the start, rather installing when I implement features with these packages.