- 50
- 238 261
Przemysław Przyłucki
Poland
Приєднався 26 кві 2020
In-depth Laravel tutorials covering building a SaaS apps using Tailwind and Vue
ChatGPT + Laravel = 🤯🤯🤯 | The FUTURE is HERE.
👇 Code repo & details 👇
In this video series, we'll be building a simple wrapper around OpenAI's client that will allow us to easily integrate it into our platform. We'll also make it hot-swappable so if we ever want to use another AI service, it'll be very easy to do so.
Repo link:
github.com/saas-laravel/laravel-cqrs/commit/2248799dfc7fc2de0b32badfbeb68a6d99ec274b
About me:
przemyslawprzylucki.com
Course website (soon):
saaslaravel.com
In this video series, we'll be building a simple wrapper around OpenAI's client that will allow us to easily integrate it into our platform. We'll also make it hot-swappable so if we ever want to use another AI service, it'll be very easy to do so.
Repo link:
github.com/saas-laravel/laravel-cqrs/commit/2248799dfc7fc2de0b32badfbeb68a6d99ec274b
About me:
przemyslawprzylucki.com
Course website (soon):
saaslaravel.com
Переглядів: 6 610
Відео
Laravel: WAY BETTER Exception handling in 10 minutes
Переглядів 4,3 тис.11 місяців тому
👇 Code repo & details 👇 In this video we'll expand on the previous video I made about exception handling in Laravel, and I'll try to propose a new solution. Code: github.com/saas-laravel/laravel-cqrs/commit/251e42c9be5df75c817d5f4295e441024da74acc Previous video: ua-cam.com/video/0AAg47xygTI/v-deo.html About me: przemyslawprzylucki.com X / Twitter: x.com/przylucki_p More content (soon): saaslar...
Laravel: DO NOT interact with 3rd party code like that... (Interfaces & DI in Laravel)
Переглядів 4,1 тис.Рік тому
👇 Code repo & details 👇 In this video we'll talk about how to use third party code, or code connecting to external services in our applications so they're easy to swap, test and maintain. Code: github.com/saas-laravel/laravel-cqrs/commit/462bf6a807bbeba9db6c1220893c2f2e32d13ca5 About me: przemyslawprzylucki.com More content (soon): saaslaravel.com
Laravel: CQRS + Event Bus | DO NOT let your DB go brrrr..
Переглядів 6 тис.Рік тому
👇 Code repo & details 👇 In this video we'll implement a *simple* CQRS system in Laravel: - we'll utilize command bus, queries and commands - we'll create separate read and write repositories - we'll have tons of fun because the real CQRS is the friends we made along the way Code repo: github.com/saas-laravel/laravel-cqrs/tree/main About me: przemyslawprzylucki.com More content (soon): saaslarav...
Laravel: 1,000,000 webhooks/minute?! Ingest webhooks like a PRO
Переглядів 4,5 тис.Рік тому
Hi there! In this video we'll create a webhook ingestion system that'll: - be able to accept *A LOT* of webhooks per second - be independent from our app, so if it goes down, we don't lose the data - never overload our application capacities Code repo: github.com/saas-laravel/webhooks-lambda About me: przemyslawprzylucki.com More content (soon): saaslaravel.com
Testing has never been THIS EASY [Free course: Great Laravel Apps #3]
Переглядів 2,6 тис.Рік тому
Hi there! In this series video I'll be showing you a couple of tips and tricks when it comes to testing I'll walk over the testing tips I like to follow: - arrange, act, assert - slow test detection - extending the base test case with useful helpers - naming conventions - php unit's data providers Resources: - Laravel's website: laravel.com - Code repo: github.com/saas-laravel/laravel-coding Co...
Laravel app can't possibly be THIS good... [Free course: Great Laravel Apps #2]
Переглядів 9 тис.Рік тому
Hi there! In this series video I'll be showing you my preferred version of creating Laravel applications. I'll walk over the project structure that I absolutely love and cover: - Creating custom src/Modules/ directory - Custom Exceptions - Custom Resources - Services - Laravel's Container resolving interfaces - DTOs - Custom Query Buiders - Enums Resources: - Laravel's website: laravel.com - Cu...
Set up Laravel projects like a GOAT [Free course: Great Laravel Apps #1]
Переглядів 7 тис.Рік тому
Hi there! In this series video I'll be showing you my preferred version of creating Laravel applications. We'll start with a project setup, in which we will: - remove redundancies from default setup - install Octane - put Eloquent in strict mode - set up static code analysis - set up styler fixer - configure CI pipeline Resources: - Laravel's website: laravel.com - Laravel Sail: laravel.com/doc...
Are VALUE OBJECTS secretly overpowered?!
Переглядів 3,5 тис.Рік тому
Morning gals and guys. In today's episode we'll talk about value objects and how they can be used. Twitter: przylucki_p More me: saaslaravel.com Website: przemyslawprzylucki.com
Fixing Laravel's BIGGEST PROBLEM (it's not what you think)
Переглядів 2,5 тис.Рік тому
Hi guys! In this quick tip I'll show you how to fix one of Laravel's most annoying things - nulls passed to resources. Website: przemyslawprzylucki.com More me: saaslaravel.com
Laravel's macros make your life EASY PEASY
Переглядів 3,4 тис.Рік тому
Hi guys! Let's take a look at Laravel's macros and how they can make your life easier. About me: przemyslawprzylucki.com Course: saaslaravel.com
WOW! Laravel's pipeline pattern is AWESOME
Переглядів 13 тис.Рік тому
Hi guys! In this video series, I'll try to showcase two good usecases for the pipeline pattern More me: przemyslawprzylucki.com Saaslaravel: saaslaravel.com
Custom notification channel in Laravel
Переглядів 2,9 тис.Рік тому
Hi guys! In this video series, we'll be creating a custom notification channel in Laravel. We'll build it to handle a super cool platform - logsnag.com More me: Courses: saaslaravel.com Personal website: przemyslawprzylucki.com
Laravel: Simple CI in Github Actions
Переглядів 6 тис.Рік тому
Hi guys! In this video, we'll be building a really simple CI in Github Actions. Hopefully you'll enjoy it! More me: saaslaravel.com Morer me: przemyslawprzylucki.com Bird app: przylucki_p
Laravel: Simple Strategy Pattern
Переглядів 3,2 тис.Рік тому
Hi guys! In this video I'll show you how to utilize a simple strategy pattern to remove some of the more complex "ifs" in your codebase.
Laravel: The BEST way to handle exceptions
Переглядів 16 тис.Рік тому
Laravel: The BEST way to handle exceptions
Refactoring real-world Laravel app. Who wrote THIS CODE?!
Переглядів 10 тис.Рік тому
Refactoring real-world Laravel app. Who wrote THIS CODE?!
Laravel: Repository Pattern in practice
Переглядів 11 тис.Рік тому
Laravel: Repository Pattern in practice
Laravel: how to deal with THICC models
Переглядів 2,5 тис.Рік тому
Laravel: how to deal with THICC models
Laravel + Service Pattern + DTOs = ❤️❤️❤️
Переглядів 47 тис.Рік тому
Laravel Service Pattern DTOs = ❤️❤️❤️
5 tips to make your Laravel application *instantly* better
Переглядів 2,8 тис.Рік тому
5 tips to make your Laravel application *instantly* better
Still using "confirm()"? Use this instead!
Переглядів 784Рік тому
Still using "confirm()"? Use this instead!
Modals in Vue. Building UI Design System [#6]
Переглядів 229Рік тому
Modals in Vue. Building UI Design System [#6]
Vue UI Design System [#5] - Icon Component
Переглядів 1,6 тис.Рік тому
Vue UI Design System [#5] - Icon Component
this is probably why the JS ecosystem always better, the vercel AI SDK is just to good to not use.
Laravel uses "messages" objects with builder pattern not DTOs but that is detail ofc :) Thanks for video
extremely like. always as usually constantly %)
When I listen to your fluent English, it sounds like you're being electrocuted or sitting on a . Tnnx for explanantion
wow
So instead of having a simple controller method that only interacts with a FormRequest and a Model, you've now added complexity with a superfluous Service class and a DTO. It may look cool, but using such a basic examples to try and demonstrate their usefulness is a mistake. public function store(StoreBlogPostRequest $request) { $blogPost = BlogPost::create($request->validated() + ['source' => BlogPostSource::App]); return new JsonResponse(BlogPostResource::make($blogPost), Response::HTTP_CREATED); } public function update(UpdateBlogPostRequest $request, BlogPost $blogPost) { $blogPost->update($request->validated()); return new JsonResponse(BlogPostResource::make($blogPost->fresh()), Response::HTTP_OK); } What should have taken 2-4 lines in 2 methods contained in 1 class became 6 methods inside 3 classes. There is a case to be made for Service classes and DTOs, but this is not one of them.
Holy f I was trying to build my own
how is it different from repository pattern?
Thnx for approach guide. But could you not speed up the words partially within eat the volume at the end of phrase.. 😅
You have great videos in laravel. keep this up
I think controller and service layer is enough for most of the laravel applications. Hence we are re creating all the method in the repository which is already available in the laravel eloquent model, it seems like a repetitive work without any additional benefit. We can just keep our controller clean and pass the business login to service class , then resolve the function my accessing database via eloquent models and then return the result to controller. in that way we can use the laravel already build eloquent powers easily and quickly.
Thank you very much!
We wanted you Przemysław Przyłucki ? ?How are you ? why you dony push video ? push video about you , channel please!!!!
Plz explain why you are using such complex things pipelines, ___invoke function, Just if condition for fillter , and if it is too mush code put it in traits
thanks for the great video
i have never worked with any php framework before. Its funny to see that back when i started learning php i designed a request handler that seems pretty similar to this piece of laravel.
I would add the transformation method to request classes. In my opinion you should not have to extend DTO classes when adding new pieces of code eg. API v2 instead you should have a method called asDto(or toDto) in the request class and call them instead of making X static factory methods. Overall great content :)
Great tips, but i more like to use different actions as class, not as a part of service. Its easy to extend from basic model to others
Any tips for getting this to work with Vue 3?
This is awesome, i hope you deep dive on DDD on the next episodes
Good Video!
Man you would love C# haha. Thanks for the video!
Use handle() method instead, not the __invoke().
Hey! How do you approach having different validation rules in the store and update actions? For example, a StoreBlogRequest which marks all fields as required, VS an UpdateBlogRequest which doesn't (for example, you just wanna update the name). Would you create more than one DTO and mark the properties as nullable?
Hey there! It depends on the situation, generally speaking with updates I'd not go with nulls because partial updates are pretty sexy - if you use spatie/laravel-data - they handle it out of the box with Optional type hint
Hopefully if you're going to be making upstream requests on every page load (or every user login) the developer will be making sure to perform reasonable caching. Since this is Laravel it should be pretty configurable, but something to be conscientious of. Also, presumably the upstream service (e.g. growthbook, in this case) is utilizing standard HTTP cache headers that Guzzle can respect and cache centrally using the configured middleware (e.g. memcached if you're on a cluster or something).
It's been cached in the video I believe. The http call is only made for fetching flags, they are resolved locally. Great piece of advice though!
Yikes. Model mutators and observers will be enough guys. But if you want to Over-engineer your code, then go on with dto or something like repository pattern. 😅
Until your app had 1200 endpoints and some places haven't been touched for years - yeah
@@saaslaravel yeah? But I prefer laravel's defaults for easier maintenance and debugging. Also KISS. Pfft
Really good man! I would like to know what you think about adding an extra layer: the repository. Because thats kinda whats going on my in job rn, laravel + service pattern + dto + repository, I feel like the Model itself could act as the Repository, what do you think?
It really depends on what you are looking for from the solution. I'd say - if you don't have a good reason to introduce a repository - don't do it. If you want to have more fine grained control over your persistence layer (i.e to handle CQRS more easily) go for repository!
Awesome video series. what laravel version is this ?
I believe it was 10
17:20 - Shouldn't our DTO have a method like toArray so that we can manually avoid passing all the parameters? I mean, they correspond to the properties of the model. Or is this a bad practice? Like this public function toArray(): array { $properties = get_object_vars($this); $array = []; foreach ($properties as $key => $value) { $snakeCaseKey = Str::snake($key); $array[$snakeCaseKey] = $value; } return $array; } and then BlogPost::create($dto->toArray());
I prefer to be explicit when possible, realistically, just use spatie/laravel-data which handles this out of the box
5:50 - what about duplication in BlogPostRequest validation for api and app? Can we get rid of it?
I didn’t know about pipeline but i think laravel provides the "when()" method on query builder instances. It’s simple and "eloquent" (pun intended 😂 ) i think but you probably already know about it. Your post seems to be for demonstrating the pipeline tool, thanks.
I think we should use RepositoryContract interfaces instead of Repository classes in the constructors of Handler classes.
You're completely right! That was a brain fart on my end!
We miss you
I may or may not be getting back soon 👀
@@saaslaravel all your your videos are inspiring! Just buil some CRM example with DB structure and it will be the,🚀
Mordo, if you use AWS there is a native way to integrate it though Event Bridge - almost no code solution and you don't pay for lambda invoke. Trust me mordziu I am an engineer. But well explained, thumb up
Prawdopodobnie najlepszy komentarz jaki kiedykolwiek dostalem, dzieki za rade xd
.
Nice tutorial! You can check ide-helper to generate model auto completion for properties. For dtos I find laravel-data by spatie a very good solution. Cheers
Yeah I use both of them in my workflow! Def worth checking out for anybody interested though!
you can go further and return dto from custom request method (getDto()) which return dto class, inside that getDto method you can pass validated() as array to dto constructor, and write typed getter methods with default values (via ??) if api or app didnt receive some values from user
Hello, I was looking at your video channel. We may be helping a company that uses secure images to increase supply chain security and help cloud native development. Would you be willing to help try their software, make a video, and help show devs how to use their tools? This is not an offer, but just to start a conversation about your willingness to take on sponsorship. Please provide me with your email if you are interested. You'd have a chance to look at their technology and decide if it's the type of software that you'd be interested in covering in your channel.
You can find my deets on przemyslawprzylucki.com
Amazing! Thank you for your lessons
huge improvement in the quality of my code after this, next level content
Am getting something went wrong error
Man, you are just awesome! Your content really helped me!
But why are not you using composition API?
How do you handle replica lag?
What font are you using on this video? Thanks!
Can this be implemented with repository pattern? to have for example in EmojiRepository in the function getFilterableEmojis() can we move here the logic with the pipeline to return just $filterable->builder->get() and in the controller to have like return EmojiResource::collection( $emojiRepository->getFilterableEmojis($request) );
Can you please put the code on git after you finish a tutorial?
When you have form request class included into ur method you dont need to do $request->validated cuz the data is already validated otherwise it throws validate exception until first line of code starts compile from function
And you dont need to use Dto u can just do create($request) //already validated clean data
Amazing stuff. I did sth weird to handle this . I added a helper method that returned an array with the key being the"Exception::class" and the value being either an array or a closure that returns an array as well this array always has a code and a message . this way I managed to also handle Laravel's own exceptions but your way of doing it is the Laravel way through the register method
Eloquent is a Repository . Don't use Repository Pattern if your Repository get data by Eloquent . it's meaningless