Customizing Laravel to do exactly what I want, thanks to macros and the container. Want to support the channel? Please get in touch! aaronfrancis.com/sponsorships
hey man, you radiate a positive energy that make me more enthusiastic to code. Your attitude, confidence, enthusiasm, curiousity, adventurous and that "My site, my video" sass is contagious! Thank you for sharing that Please keep creating videos. You rocks!
YES, reading Laravel's source files is a game changer. Not only you understand better what is the thing doing exactly, but you can find a lot of other useful functions and snippets in the process. And also I have been using DB query builder macros to add new functions to it, like one that automatically selects columns with an alias name, based on a map array loaded at the macro's definition, that maps column names.
Ay Ay Ron (sorry, intrusive thoughts won), this is the first time I'm seeing someone actually go beyond the basics in Laravel and talk about approaching Laravel not from a purely consumeristic perspective, but rather from an engineering perspective.
I think I might need to watch this video a couple more times at 0.5 speed to fully grasp what I just saw. It's looks easy but magical at the same time.
Fun video! It's always interesting to see what's under the hood and all the undocumented ways you can use the framework. An approach for this particular problem that I like to use is to have a "url" attribute accessor on my model, and have that be responsible for handing me the proper URL. That way, I don't even need to remember my route name throughout the project.
Great video! Really enjoy hearing you think out load when you're trying to figure things out. I think a scripted screencast is very valuable but watching an experienced developer wrestle with things gives a different look. Thanks Aaron! -Mike
Holly cow, I always saw you around X, but I never thought too much about you. But after watching this my jaw dropped, we must be on Laravel lore forever as one of the greats.
I just want to reiterate how much I appreciate that you made this. There's a LOT of beginner content out there. I really appreciate you making things on intermediate and advanced topics, too. I feel that the way in which you do it (showing the process, rather than just the result) makes it less intimidating. Finally, you're not solving a specific problem, you're using the problem to showcase a method of finding a solution, which is awesome as well! You got me gushing over how much I appreciate this video!
This is a great video about how to think! I would personally keep the original route URL and then redirect to the external URL in the show method, so when we add page statistics, trends, etc., that would also work for the external posts as well.
"I'm just going to leave it as it is." That's a Perfect approach. Nowadays, developers spend so much money and time on things that someone may ask to do something with them one day. Let's deal with that later when it is needed!
I have typed dd('here') and dd('1234') at least 7 million times in the last 10 years! I quite like Spatie's Ray product which essentially does the same thing but feels less blunt 🙃........Very relatable and enjoyable video - keep it up!
Great video, I absolutely hate this with every fibre of my being due to the sheer complexity introduced here 🤣 but it's fascinating nonetheless. Would love to see more videos like this! Thanks for sharing
This is funny... I watched this video a couple of days ago and today i found out a problem with Laravel+Mongo+Failed Queues and remembered of this video and implemented an 'extend' to 'fix' a laravel base class... 😅 Thanks man! (The base class isn't Macroable, tho, but i have access to the needed params from the $app instance 👌)
Like the idea, I would probably pull the macro out into a mixin and stick both the generator & mixin in an Extensions directory to signal it’s extending the framework. :)
I both love it and hate it. That kind of stuff bit me a few times so I've learned to settle for much more boring solutions. Very entertaining video though. I'd love to see more advanced content like this.
This looks so terrible and so impressive at the same time. It`s just amazing to know that you can do it even in such pretty weird way. Great video Aaron, thank you so much for such high-quality content!
9:03 I didn't know that people speaking english know the german word "verboten" which means forbidden 🤔 Apart from this, I really appreciate that you make more videos now. They are so high quality, even the fact that there is close to no cut when you are speaking... wow. In my videos I mispronounce something every other sentence 😅 (German is a difficult language 😂) You are also explaining the things very close to how my thought process is. Hoping to see more of these kinds of videos!
Haha sometimes things pop out of my mouth and I'm like... where did that come from! Glad you enjoyed it :) I enjoyed making it. I'll do more videos like this one!
Routes are cached & serialized, so Closures are probably not great. You should try it with cached routes. Empty weakmap? But it is fun making computers do what you want! Just test it with production config before you go to production :D
Hi, Aaron. I have a question. Not directly related to Macros, but Laravel. 😁 When it comes to choosing a CMS to use with Laravel, which have you used before and which one(s) would you recommend for better editorial experience? Thanks.
This feels like a lot compared to just adding a redirect within your `ArticleController`'s `show` method at the start that does the sniff test for external, and responding with a redirect. Cool to see the process you followed for utilizing macro's though 😁
Not an SEO person, but I imagine that will have some sort of SEO implications. I would imagine linking directly to the external URL is better than having the crawler follow a URL only to find it redirects you to an external site. Also it would be more transparent to the user to be able to see that the URL is external. But I do agree that your solution would be easier to implement 😂
Cool idea and useful to see your way of debugging and unpacking framework code. But I was scratching my head the whole time, can't this entire thing be handled by 1, maybe 2 if/elses to returns the correct url? 🤔
I use a top of the line Macbook Pro, and use Sail instances for dev (with a proxy manager layer to run multiple at the same time). The further into a project I get, the more painful it gets to do a quick dd() or run phpunit tests. Do you have any tips on dev environment setup and speed?
Oh, so that is what the macros are! Also how would you document what you have done so you can understand it in 6 months when you have to work on that feature again?
@@aarondfrancis Something like this in your service provider? I'm just a jr dev don't listen to me lol. `public $bindings = [ 'url' => MyCustomUrlGenerator::class, ];`
It's very robust. But if you don't like it, remove the batteries and put in your own. I use LDAP at work with Laravel, for example. We also have a few apps that use SSO with custom IDP. On most of my personal projects the built in stuff is perfect.
Route would always consider your domain. You just need to construct your external urls any other way other than route methods. It’s a very strange video, creating a problem which doesn’t exists. At least till now 6:26
Sorry but this is wrong in every sense possible. And not fun at all for me. Think of new devs who watch your videos. Anyways, you do whatever you want. I am no police. Have a great day 👍🏼
Great video! This is my problem with modern "Laravel" PHP. Antipatterns, the interpreter has to parse all these 3 million layers. Unlike Java or C#, which is compiled down, it's fine to have so many layers.
If it were me I would just @if($article->markdown_file) href="{{ route('article.show', $article->slug.$article->public_id }}" @elseif(!$article->markdown_file && $article->external_link) href="{{ $article->external_link }}" @endif Am I cooked?
No more cooked than the rest of us! Honestly no, that's totally reasonable. I'd probably wrap that up in a method in the Article model itself so that it's easier to use throughout the app, but it's not crazy!
