You mentioned buttons behaving weirdly when inside a flex container. It's because they try to fill up the whole height of the parent. Putting an "align-items: center" (or "items-center" class in tailwind) solves that issue so you didn't need to put it in a separate div since you already gave that class. Amazing course btw, even though I'm above intermediate in Laravel I still like watching these kind of videos.
I am getting this error with this environment: PHP 8.3.8 - Laravel 11.20.0 Symfony\Component\HttpKernel\Exception\MethodNotAllowedHttpException The DELETE method is not supported for route jobs/15. Supported methods: GET, HEAD, PATCH. what could be the possible issue?
Hi,I am getting the same error for the PATCH route, were you able to find a fix for this? edit: I forgot to change action="/jobs/" TO action="/jobs/{{ $job->id }}" at 12:57 I just wasted like 2 hours trying to find the error 😭😭
Is there a reason for saying an item is "persisted" to the database rather than saying is it "saved" or "written" to the database? I have no objection to "persist" --- I'm just wondering why it's used rather than "save" or "write", which seem more natural. (After all, the Laravel method is "save()".)
Data can be saved temporarily, it will go away when restart. Or it can "Persist". In programming the persistent is the common term. (At least in the Android developer ecosystem)
it feels to me that should be implemented at the button component level, a "require confirmation" attribute intercepts default submit via JS and displays a confirmation popup that has a confirm button linked to the original form, a backend implementation would be a waste of resources I think
@@Laracastsofficial i was really looking forward to a Laravel REST api full course but what the 3 free episodes showed me is bad REST api practices (naming routes "/edit", "/delete" instead of using http methods in the same URL), bad code practices (using a single character for status instead of a php ENUM or at least a readable string), it blatantly jumps steps (starts working in the api file when laravel no longer ships with API files by default, and the course was released after laravel 11), looks like a mess to me and I wouldn't like to learn from a bad resource, by any chances are you planning to do a Laravel REST API course yourself? 100% paying for your content
Bravo master
You mentioned buttons behaving weirdly when inside a flex container. It's because they try to fill up the whole height of the parent. Putting an "align-items: center" (or "items-center" class in tailwind) solves that issue so you didn't need to put it in a separate div since you already gave that class.
Amazing course btw, even though I'm above intermediate in Laravel I still like watching these kind of videos.
Interesting information about the form attribute in the button. Thanks for these videos, I always learn something new. Eager to see the next episode.👍
I just picked this episode from the entire series and it was the best tutorial I watched in years!
that is amazing❤🔥❤🔥
thank you bro
That simple form attribute in the button tag made my jaw drop. I solved it with JavaScript until now. Time for some refactoring on my components :)
Same, I was shocked about 5days ago while working on a project.
ChatGPT suggested that when asked to refactor.
0:20 maybe 20🤣🤣
❤❤❤❤
I am getting this error with this environment: PHP 8.3.8 - Laravel 11.20.0
Symfony\Component\HttpKernel\Exception\MethodNotAllowedHttpException
The DELETE method is not supported for route jobs/15. Supported methods: GET, HEAD, PATCH.
what could be the possible issue?
Hi,I am getting the same error for the PATCH route, were you able to find a fix for this?
edit: I forgot to change
action="/jobs/" TO action="/jobs/{{ $job->id }}" at 12:57
I just wasted like 2 hours trying to find the error 😭😭
@@pootisbardo019 no I didn't find a fix for it
hello
if you have page expired 419 error
try to add
value="DELETE"
Delete
in your html button
it should help
when i inspect in the browser the hidden form became inside the other form
First Viewer❤
Is there a reason for saying an item is "persisted" to the database rather than saying is it "saved" or "written" to the database? I have no objection to "persist" --- I'm just wondering why it's used rather than "save" or "write", which seem more natural. (After all, the Laravel method is "save()".)
Data can be saved temporarily, it will go away when restart.
Or it can "Persist".
In programming the persistent is the common term.
(At least in the Android developer ecosystem)
It's just jargon for saving. When in architecture we talk about data storage we usually refer it to the persistence layer.
Very good, but I would like to see confirmation before deleting!!
it feels to me that should be implemented at the button component level, a "require confirmation" attribute intercepts default submit via JS and displays a confirmation popup that has a confirm button linked to the original form, a backend implementation would be a waste of resources I think
Currently building REST API using Laravel for the first time and the timing for these videos could not have been better! 🎉
#Goldenstuffrighthere
We have released full course about API building on laracasts.com/series/laravel-api-master-class
@@Laracastsofficial i was really looking forward to a Laravel REST api full course but what the 3 free episodes showed me is bad REST api practices (naming routes "/edit", "/delete" instead of using http methods in the same URL), bad code practices (using a single character for status instead of a php ENUM or at least a readable string), it blatantly jumps steps (starts working in the api file when laravel no longer ships with API files by default, and the course was released after laravel 11), looks like a mess to me and I wouldn't like to learn from a bad resource, by any chances are you planning to do a Laravel REST API course yourself? 100% paying for your content
@@laikmoshwa1028 thank you for the review