@_Codito_ I agree with your points. It’s essentially mis-using a singleton data store that persists throughout the request. Something about giving a person a hammer and looking for nails to pound.
@kyleshevlin If it’s knowledge my company lacks then I would consider hiring an external team to get started with it but I would also want my team to be involved as they’ll end up being the ones maintaining it.
@pieterbeulque@frankdilo@jessethanley Having worked on an e-mail marketing SaaS, I can confirm that ensuring deliverability is almost a job on its own.
Most transactional e-mail services also don’t allow using it for marketing purposes, (or provide a specific set of IPs for that reason).
@calebporzio We recently launched an app that uses Filament for a back-office to which some users had access.
While we could use Filament components without using Livewire for the CRUD screens we did have a lot of custom components and screens where knowing Livewire helped.
@garyclarketech The point of an enum is that it consist of a set of predefined values and it can be reconstructed from that value through tryFrom and from methods.
Why would you want to serialise this instead of using the scalar value (and gain language interoperability for free)
@_Codito_ Good for you for sticking with your vision! If they want to build a tool they shouldn’t abuse a proper useful tool for the mere purpose of a joke.
How to make upgrading dependencies a pain. Each to their own but I’m genuinely getting concerned about some of these things that are getting endorsed. It gives a wrong signal.
@pieterbeulque See this quite often, there’s always some divide (dare I say hostility) between engineering and sales. It’s amazing what you can achieve by listening to their input and involve them more closely in a product development cycle.
@jordankdalton I was under the impression the fake was for an external API but looking closer at the snippet you’re testing an endpoint in your own application. Not sure why you’d want to mock that during a test though?
@mabdullahsari That approach for read models is really nice. In the past I’ve solved it with plain PHP classes that are created through a repository from the original model but you obviously lose a lot of the flexibility of Eloquent and can no longer use relationships.
@_Codito_ It’s a sad reality. In the past I’ve always used PHPCSFixer directly but recently switched to Pint because it’s easier to convince others since it’s a Laravel thing. I do hope we get a more streamlined process so newer versions are integrated faster.
@NMBS zou leuk zijn moesten jullie afgelaste treinen ook effectief aankondigen ipv in de apps te tonen alsof ze rijden / vertraging hebben, al meerdere keren gehad dat een trein simpelweg niet komt opdagen de voorbije week (S93279 / IC3613)
@_newtonjob I fail to see how using a try…catch statement results in “messing up your controllers” though, the options you provide are both viable but my preference is making exception handling more explicit.
@jszobody@awcodes1 Does Livewire’s temporary files support chunking? I know that S3 has a multipart upload API (https://t.co/vtu6S1KIn3) but I’m not sure if Livewire makes use of that?