Great Content, friendly reminder, be careful with the empty space.
@abdelbarimessaoud24226 күн бұрын
wouldn't this make the users table have multiple NULL columns for each type if they have different fields (other than the parent's one) ?
@PaulAllsopp-rh5gbАй бұрын
You have no idea what you're talking about
@PaulAllsopp-rh5gbАй бұрын
deletes my post...lol
@alexalex6643Ай бұрын
yeah PHP suffers without "normal arrays"
@vedovelliАй бұрын
Thank you!
Ай бұрын
👊
@chechomancr4Ай бұрын
Min 13:20 the class "UserSetthings" can be "final readonly class UserSetthings".
@vuejs12 ай бұрын
Brilliant explanation
Ай бұрын
Thank you
@AhsanKhan892 ай бұрын
Can't we use it with api?
Ай бұрын
You can
@AllanSavolainen2 ай бұрын
I would probably do this only if the class is used more than 3-5 places, if it is less, always go for array for simplicity.
Ай бұрын
It's not just about simplicity; an array doesn't enforce any types, is not automatically-refactorable, etc
@AllanSavolainenАй бұрын
It is super easy to refactor when you don't have to care about types until you actually use the value to something that cares of types.
Ай бұрын
@@AllanSavolainen what I mean is that objects are recognized by IDEs and SA tools, so you can do automatic refactoring. Arrays are generic constructs that do not offer that possibility.
@TerabyteTy3002 ай бұрын
Brother excellent video!! It’s so good getting into the details. I appreciate how you make it digestible even for someone new like myself. Really helps the info stick.
Ай бұрын
thank you!
@nelsonmutane13722 ай бұрын
Porque só vejo esse video hoje
@invincible97242 ай бұрын
Useless video no example nothing
@darz_k.2 ай бұрын
Why didn't you just rerecord the video? I get an error message on your video before the error even comes up - I won't watch the video now! (that's advice)
Ай бұрын
huh?
@darz_k.Ай бұрын
Exactly.
@sonoftroy85722 ай бұрын
Flowcharts are important to do before programming
Ай бұрын
they are!
@sonoftroy85722 ай бұрын
Agreed
@ElvisIsking-u1m2 ай бұрын
I found your channel because of STI. I'm hooked. Excellent how you get things working and show it, then move things from the child model to the parent and it's still working, then remove it to a trait. It demystifies what the packages do and that's really valuable. The depth of explanation is really thorough and the pacing works really well for me.
2 ай бұрын
Thank you so much! I’m glad you’re enjoying it. ✌🏻
@ClawHammer233 ай бұрын
PHP 5.6?
@josiasvelazquez10953 ай бұрын
Excellent video! What font do you use? It's awesome.
3 ай бұрын
Thank you! The font is Operator Mono.
@josiasvelazquez10953 ай бұрын
🫶🏻
@florisvandenberg74243 ай бұрын
This is basically the datamapper pattern inside the activerecord pattern. Horrible. I really, really, really, really hate Eloquent and Laravel as a whole.
@mkGarf3 ай бұрын
I would only add that, as a general rule, it should be understood that arrays are much more efficient in terms of memory and processing. Therefore, for any process that requires iterating over collections that can grow large, arrays should definitely be used, and objects should not be used at all. For maintainability, architecture definitely matters. Given the above, as a general rule, I would use objects as a means of communication between software components within the defined architecture, but the implementations for handling large data collections should be abstractions that use arrays behind the scenes. Let's say that algorithms, which need to be implemented correctly from the start and rarely modified, should definitely be implemented using arrays.
Ай бұрын
agreed
@marceloAK13 ай бұрын
Great video. I've been using this approach a lot lately. How do you work when you have an attribute in UserSettings that must be set after the object creation and need to use it inside the notifyUser function? When do you check if the attribute was set or not? Thanks so much.
3 ай бұрын
Can you exemplify? If the function takes an object as an argument, and requires property X to to be set, you can add a guard clause - e.g if ($someObject->property === null) { throw new SomeCustomException(); }
@marceloAK13 ай бұрын
Thanks for that, that's I wanted to know.
@david.arl143 ай бұрын
i do this on last my project, for Entities in laravel implemented clean architecture. and very helpful for maintaince data return from services and repositories
@JustSomeObject3 ай бұрын
what if i want to early exit from say the 2nd pipe and skip the rest of the pipes?
@codyscorner18293 ай бұрын
Well this is not a array. An array is one data type. When you are putting in different data types it's more a data container or table.
3 ай бұрын
It’s an associative array.
@jediampm3 ай бұрын
Its only an assoc if it has keys as string, otherwise if it is a list of objects so it is an indexed array. if you have an object and cast to an array, it will be an assoc array. to sum up, for example, if you fetch from a db more that one row, than will be a list of array assoc or stdclass ( so indexed array), only a row turn into stdclass or array assoc.
@saytaimoor3 ай бұрын
Video title is misleading. A handy solution when it come to simple read-only operations sure, but it is by no means an "alternative" to the arrays. Think about what you can achieve with arrays when it comes to data manipulation and processing. Not to mentioned numerus PHP's build in and custom-tailored functions to process data.
3 ай бұрын
You can achieve all of that still. Anything specific you're thinking about?
@QuintessentialDio3 ай бұрын
Years of writing PHP, and i still learnt something new today, thanks lad.
3 ай бұрын
Happy to help!
@cafnix3 ай бұрын
My boss, I taught you have learnt everything you need in PHP
@kvelez3 ай бұрын
Cool do more PHP videos and courses.
3 ай бұрын
will do!
@xtremescript3 ай бұрын
What you call arrays in other languages is actually vectors if you are coming from an actual programming language.
3 ай бұрын
Actually, arrays and vectors are different things. A vector is essentially a dynamic array.
@jediampm3 ай бұрын
Actually, in languages like c, c sharp, java and go, vectors has a fix length / one dimension and only allow primitive types. So an array, arrayList, Map, etc, are dynamic vectors that allow more complex types and the length is dynamically updated.
3 ай бұрын
@@jediampm It’s the other way around. e.g in C# an Array has a fixed size, while a List<T> will grow/shrink dynamically.
@jediampm3 ай бұрын
your are correct, my mistake writing for too long PHP that mix up concepts like array / matrix, etc in another languages, not only C Sharp.
@DavidSmith-ef4eh3 ай бұрын
Yeah, I do this all the time. Makes refactoring much less stresfull. Also, using Propel ORM for the sam reaoson. It allows you to change the database schema without having to worry that code will break. Too bad worse ORM solutions like Eloquent are more popular than Propel. I guess PHP developers suck.
3 ай бұрын
I’ve never used Propel. I’ll take a look!
@DavidSmith-ef4eh3 ай бұрын
it seems to be abandoned.. very slow updates. abandoned project. I tried to find an replacement ORM but none of them is as good as propel.
@BrunoBernard-kn6vt3 ай бұрын
It is Value objects ?
3 ай бұрын
They can be VOs, but not necessarily.
@BrunoBernard-kn6vt3 ай бұрын
thanks for replying ! Ex. Let's say I have an action, i use an object instead of a array to transport the value right ? basically it reduce the need for Laravel Validators. right ?
3 ай бұрын
@@BrunoBernard-kn6vt That’d be a DTO. It doesn’t eliminate the need of a validator because you still want to validate messages at the borders (e.g HTTP). A value object would be - for example, an Email object, that could enforce the string to be a valid email, a ZipCode object, or a Money object. These would typically be used in models (through cast operations in Laravel).
@BrunoBernard-kn6vt3 ай бұрын
Thank you so much for clarifying, and if i have to organize these types objects where should I namespace it? Enums goes to Enums folder. Value Objects goes to ValueObjects folder. Objects folder perhaps?
@khangle68723 ай бұрын
One (still) useful usage of array is a pseudo Tuple: function doSomething(){ if (somethingWentWrong()){ return [null, new SomeBusinessException()] } return [SomeDto, null]; } function someConsumer(){ [$data, $error] = doSomething(); // } A pseudo Result<T> monad, but until PHP had generic, Tuple will have to suffice
3 ай бұрын
Yeah, I find usages where it’s short-lived perfectly valid.
@OleksandrAndreiev3 ай бұрын
Of course this is good approach to replace assoc arrays with objects, but it would be nice to see such approach in framework configurations instead of arrays/yaml files.
3 ай бұрын
Yeah, I’d very much enjoy that.
@drugoviic3 ай бұрын
laravel throws errors when you access a key that isn't set i thought that was the default behaviour, maybe i don't know php that well
@TotoTitus3 ай бұрын
this has become a LOT more relevant since PHP introduced constructor-defined readonly properties. Creating value objects, DTOs whatever is now pleasant and elegant.
@LucasAlves-bw9ue3 ай бұрын
Thats solid principles applied into php. Thats awesome!
3 ай бұрын
Glad you liked it!
@wraithlotus3 ай бұрын
It had never occurred to me to treat arrays as objects.
@easyvideott75053 ай бұрын
This is all dependable on the context... good thing for complicated data but overkill for some simple data... Generally the video is a good hint about what can you do in PHP as a programming language. "Chose your 'weapons' wisely!"
@CottidaeSEA3 ай бұрын
@@easyvideott7505 Simple data becomes complex when suddenly you need to check what to send to a function all the time. When something is added but not documented. When something is expected but not provided. A class can give you default values. An array can't. Create a class, save your colleague.
@easyvideott75053 ай бұрын
@@CottidaeSEA Exactly! If you need data complex as that, surely it would be better to make a class and pass the data as an object. All I wanted to say in the previous comment is that it would be wrong to say: "Never use simple arrays in PHP, always use Class objects".
Ай бұрын
"Simple data becomes complex" - I"ll save that!
@brunoggdev63053 ай бұрын
The timing for this video couldn't be better as I was literally talking about these exact points yesterday with my team. Great content man, kudos from Brazil! Also it was awesome to see u on Laracasts as well 🤩 Parabéns meu bom
3 ай бұрын
Valeu!
@AsmitNepali-hb9vh3 ай бұрын
Nice video, what if we have numbers of array elements like current_period and previous_period, is it good to pass on constructor ? kzbin.info/www/bejne/bZibiHZ3pc6tZpY
@CottidaeSEA3 ай бұрын
Honestly, I'm quite baffled that PHP devs don't use classes more. "We need to pass an array to this function" okay, so use get_object_vars? Create a toArray method? The good thing about having a class is that you can add default values to the state and easily create a copy of it, along with a strict schema to follow.
3 ай бұрын
Yeah, I’m honestly surprised by some reactions to this video, which I considered fairly mild.
@gamersunite90263 ай бұрын
your username in comments doesnt render. wtf?
3 ай бұрын
Yeah I’ve noticed that as well lol
@pfqniet3 ай бұрын
By far the biggest thing to be aware of with Swoole is that if your code encounters an error, the entire worker has to be restarted, which kills all requests that it had been handling concurrently at that time. In FPM, just that request is affected. You have to be a LOT more defensive with your code in Swoole, which can be difficult sometimes due to PHP's ancient error model.
@ricko133 ай бұрын
Mateus, I didn't watch the whole video, but it appears you're trying to do what the *spatie/laravel-data* package does, just take a look a it
Ай бұрын
It's not about a package
@LewisCowles3 ай бұрын
This is also what JS has... Array in JS is an Object with some additional symbols.
@ihorrud50883 ай бұрын
Hi! As I understood we use just plain php classes(like UserSettings) when we want to use it internally, probably withing one layer. And if we want to pass data from controller to service or other layer we use DTO, right?