Static Methods in Laravel/PHP: When and How?

Подписаться 140 тыс.

Просмотров 16 тыс.

50% 1

This is a shortened video version of a premium tutorial from Laravel Daily.
Full tutorial: laraveldaily.com/post/when-no...
- - - - -
Support the channel by checking out my products:
- My Laravel courses: laraveldaily.com/courses
- Laravel QuickAdminPanel: quickadminpanel.com
- Livewire Kit Components: livewirekit.com
- - - - -
Other places to follow:
- My weekly Laravel newsletter: us11.campaign-archive.com/hom...
- My personal Twitter: / povilaskorop

Хобби

Опубликовано:

13 июн 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 35

@guccilive100 10 месяцев назад

I don’t know if you are a kind of super hero for me, but each time when there’s something that blocks me or can’t understand… then booom!! here you are with a quick tips video about it. Can’t thank you enough… 🎉❤

@roberrt8386 11 месяцев назад

Static methods are great to initiate the class itself eg. ::fromValue

@fredvuni6240 11 месяцев назад

I've been racking my brain over this concept since yesterday. Thanks!

@roman_zabigaliuk 11 месяцев назад

This is one of the topics where I feel immature. All my methods are static and I feel comfortable with it. And I uderstand that adult developers don't do that, and I need to step over myself once. Thak you for your reminder to me.

@matrixlander85 11 месяцев назад

Great video with multiple examples

@SussanRai 11 месяцев назад

Static method is good when it doesn't depend on any dependency injection

@dominiks5318 11 месяцев назад

😅 I think author doesn't use Mockery and don't have the knowledge how to properly test the application.

@guccilive100 10 месяцев назад

@@dominiks5318I tried mockery on a static method and was getting error that method was call 0 time but expected 1 and when I changed to be not called then the error the method was called 0 time but expected 1🤷🏿‍♂️

@giacomogaravaglia6742 11 месяцев назад

use NON static method (/classes) if you need to inject it via dependency injection.

@AndyTalbot 11 месяцев назад

Are they in any way better for performance? I tend to avoid them, and watching through the video it felt like you would generally too, but then you gave some very interesting examples at the end, and now I'm thinking of a few places in my projects where I could in theory use them.

@LaravelDaily 11 месяцев назад

No, you wouldn't feel the performance difference

@johnnyw525 7 месяцев назад

@@LaravelDailyYou wouldn’t feel the difference, but why why instantiate a class when you don’t need to? 🤷‍♂️

@johnnyw525 7 месяцев назад

It’s really basic: Use static when the method (function) doesn’t need to belong to an instance of the class. Ie. Does the class need to be instantiated for the function to operate? You can mix and match perfectly fine. There’s no need to instantiate a class if you don’t need to.

@OliverKurmis 7 месяцев назад

You always say "initialize" the class, but you mean "instanciate" the class. A class instance is an object, a data structure bound to the class methods. The object can be initialized with the help of the special "__construct()" method. Using static functions there is no object, but just a call of a function.

@guccilive100 10 месяцев назад

Does anyone can point me to how to mock a static class?

@LaravelDaily 10 месяцев назад

My tutorial specifically pointed out this reason of why NOT to use static classes. They are not mockable, maybe some tools are capable of it but I haven't done it

@ricohertha3537 10 месяцев назад

@@LaravelDaily static methods

@free2idol1 8 месяцев назад

If you want to mock static class, then it is better to first make that class as normal class (non-static), then make a facade class as a wrapper around that underlying class, then you can use mocking function provided by laravel to mock Facade.

@richardwheatley7194 11 месяцев назад

Why use them at all? What are the benefits?

@LaravelDaily 11 месяцев назад

No need to initialize classes manually if you don't want to

@LeTrolli 11 месяцев назад

simple rule, do not use object just to call functions

@johnnyw525 7 месяцев назад

@@LaravelDailyYou say “initialise” but you mean “instantiate”: Create an object from the class. I’ve never heard “initialise” in this way before? Is it common?

@BlueJDev 11 месяцев назад

All that useful information and explanation, then there's me looking at the last example wondering why the functions have $value parameter but use $this-name and not $value in the function... Lol Not even a $value ?? $this-name

@zkabadu 11 месяцев назад

Just don't mix and match static and non-static methods in service classes.

@johnnyw525 7 месяцев назад

You can mix and match.

@zkabadu 7 месяцев назад

@@johnnyw525 yeah, you can, but you shouldn't.

@premce45 5 месяцев назад

@@zkabadu Why ?

@zkabadu 5 месяцев назад

@@premce45 I like to keep my classes consistent. Either I use the service class as a kind of utility class, then I would use static methods. Or I use dependency injection and then I will use non-static methods so I can access the injected dependencies. But I don't want to mix and match both responsibilities in one class.

@rs-nm7hp 11 месяцев назад

thanks for this video @povilas

@paulfontaine7819 11 месяцев назад

4:00 "that may work but it does not feel clean too me. I'm just personally not a big fan" . Please instead keep explaining when it does not work. Add you say some people feel they should never use static at all and thankfully you explain when it can be used.