@davorminchorov Nice read. It's good you explained what's the CategoryReadModel. I guessed it would be a DTO but looking at the namespace and seeing it same as the eloquent model got me wondering.
@PovilasKorop@buffer Not here too!!! I'm seeing 11:11 on my clock everyday... even when I have the urge to look at the clock, I force myself not to, and delay looking for a couple or minutes, and guess what, I still land on 11:11.
Today I didn't look at the clock yet but, ur post has it many times π
Daily resource #133
Almost every Laravel-app needs toast notifications, but do you make them yourself or not? And do they work with Livewire?
@usernotnull created a great solution for TALL-apps.
β https://t.co/jR8riJ9dwcβ
@ryangjchandler There's also an issue with entangle. It was missing the debounce feature (rare use case but still...) forcing me to use wire model. I opened a discussion here https://t.co/quBFyo4bdP
@ryangjchandler I'm guessing it depends on the use case. Most of the time I go with x-model and entangle it to cover all use cases, but when I feel I won't need to use the value in alpine I just quickly wire:model with the emmet autofill 'wim'
π₯ #Laravel v9.2.0 added `Attribute::with`
It's a very simple change but makes the code look more elegant.
Luckily, the change is really simple if you already adopted the earlier `new Attribute`. Global search & replace `new Attribute` -> `Attribute::make`
@LukeDowning19 I always meant to write a command that does something similar, but never did. Thanks for sharing!
I submitted a feature req on github which I think would be nice to have.
@tobias_petry Hey π
I usually stick to auto inc ids with uuid on another column for public facing tables. Have you checked performance of snowflake ids? I have not used them yet, but if there is no significant impact on performance, would you recommend them over my first approach?
@peterfox@PovilasKorop True, that's exactly what came to my mind. The 'to route' action intention isn't as clear as 'redirect to route'.
I guess I'll eventually just follow the framework convention in any case π€·ββοΈ
@PovilasKorop That would be amazing. That class can do so much, but with bad docs most people don't know about it, let alone use it instead of reverting to custom made "inferior" methods.
@PovilasKorop You worked hard to reach where you are. Now you can afford to relax.
Pains me to see younger ppl adopting this mentality too early (having to rely on others for support). I think we all know people like this.
@PovilasKorop Between that, your book (and your github tips repo), and a couple of others who mentioned they're writing books about laravel tips... The amount of resources the community has is amazing.
So many goodies in the upcoming #Laravel 9!
If your project will not be upgraded to laravel 9 any time soon, you can still take advantage of the new str() helper by adding the below code in your helper file.
The shorter syntax, without sacrificing autocompletion is great!
π₯ #Laravel Snippet
Here's a helper function that eases calling faker functions.
In factory classes you usually use $this->faker(). Using the below function, you can call faker()->___ anywhere in your project, with auto-completionπ