@jbrooksuk @laravelphp Will existing Forge+Envoyer setups be able to “migrate” existing apps to just using Forge for atomic deployments? And how do Forge atomic deployments differ vs Envoyer (if at all)? Thanks!
@joshmanders@filamentphp Does it work again after running php artisan view:clear? I had this issue and it would work once, then stop working again until I did that.
@CodyPChristian@driesvints Same here, it’s a very good product. Very fast to prototype with, easy enough to extend with custom code when you need, one-click publishing, what’s not to love
@tjthedev I had one in 2023, it took me by surprise after 15 years of repressing my curiosity towards it 😂 I still prefer procedural but learnt a lot of transferable skills, now I code in more of a hybrid style when it suits. No regrets, and feels like a rite of passage in hindsight.
@Sairahcaz2k@Cloudflare Do you know if it was caused by DNS, page rules, WAF, or something else…? Without knowing the context it’s hard to rule out a misconfiguration/server issue entirely.
@benjamincrozat@mateusjatenee Interesting discussion, I feel compelled to give a real-world example in favour of @mateusjatenee’s approach. This is just a small section of the /app directory from my Laravel-based SaaS platform. There’s 7 years of code, over 12 distinct services. This works great for us!
@crimebucket@robertskmiles Financial systems are accountable to 2 parties. If the seller rigs the system in their favour, the buyer has their own audit trail as a defence. But voting systems must preserve privacy between participants – so if electronic votes are rigged, we’ve got no way to know or prove it
@laravel_idea@peterfox I think we’re talking about the same thing. To be clear, I also see throw_if() showing an unhandled \Throwable. It’s the next echo line in my screenshot which PhpStorm marks as “Unreachable statement”. Can you reproduce that on the next line after a throw_if(false)?
@_newtonjob This is just what I was looking for the other day 👀 I had an Image object which could show up randomly in an array of strings. This makes rendering an <img src… /> nice and easy in Blade, whilst letting __toString() return just the URL without any markup elsewhere. Thanks!
@TodePond Are you evaluating depth-first or breadth-first? I’ve built a similar kind of thing and curious how you’ve approached it, both sides have interesting tradeoffs. Love the simple UI, I bet there’s a lot more going on behind the scenes too.
@peterfox The only rule I had trouble with was LARAVEL_IF_HELPERS. There’s a very annoying bug in PhpStorm, which has been parsing conditional return types incorrectly 🤦🏻♂️ I’ve reported it, hoping they fix it soon.
@peterfox Absolutely, will do. I applied 30+ rules to a side project earlier and it worked flawlessly 👌 Planning to run it over 7 years’ of production code in the coming weeks, that’ll be a breath of fresh air for sure!