Laravel Code Review: Debugging, Repositories and Base Controller

A code review of one of you guys who asked for my advice based on their private code repository. Let's take a look!

00:00 Intro
01:37 Error 1. Admin Dashboard.
03:37 Error 2. Registration.
06:05 Error 3. Failing Tests.
10:16 Models as Repositories? Not sure.
12:34 Base Controller or Config?
14:55 Small Things Here and There

Related videos:

- - - - -
Support the channel by checking out our products:

[tiagotheoliveira]

I prefer the long videos. More tips, and more learning.

[darkmode]

Short or long videos, I still watch it. Thank you!

[krzesimirbonobo]

Longer code reviews are better - more chances to a viewer to find and learn new things and concepts or stuff that he/she know, but just forgot about it

[shakilnadim]

short or long doesn't matter to me as long as i get good advice. And that's exactly what i get. thank you.

[JouvaMoufette]

Re git commits:

A well worded commit summary is usually about 50 characters or less can usually finish the following sentence: "When this code is merged, it will ____."

Examples:
Migrate models into Model directory
Add missing class to card div on item edit page
Refactor shipping status notification logic

If you need more detail, you add a blank line and then you type as much as you want (usually 80 characters max per line).

I also recommend ending with another blank line followed by a ticket number or link to a ticket if the commit you're making is related to a ticket in a ticket tracking system such as JIRA

[abdulhalim]

doesn't matter how long your video is, I am here to watch till the end.

[travholt]

I have no issues with this length of video!

[mccheesy]

I recommend looking at the Conventional Commits project and related tools for some help on making better commit messages. This can also be combined with Conventional Changelog to produce a useful change log from your git log!

[marcelrozendaal]

I really like this debug videos, the longer the better :) thank you for doing this for us...

[ajithlal]

Long videos are also good. Please Do more videos on testing.

[hosamgnaba]

i think my friend longer is better as long as it is worth it like this video, there are tones of information in this video and it helped me a lot as a juinior developer, so thank you so much

[basittope]

Long video is cool. No need to rush.
Thanks For your Support.

[zls]

thanks Mr Povilas for reviewing my Code. I enjoyed it and tons of things to learn.

[SouravTah]

Every word from you is motivational. Thus longer videos as this one are welcome. Longer videos = better understanding & knowledge 👍

[AndersFloor]

Once again very informative, thank you. I have no problem with longer videos like this. You are giving great advice and feedback while maintaining a good tempo and I could easily watch for an entire hour.

[showunmioludotun]

This is long but worth it.. Thanks for the review session

[nigelpanashemakwara]

Thank you for the review, i was able to learn one or two concepts

[mateusssantana]

You're the best, man. I love your videos. Great tips and much knowledge! Thank you :)

[atatopatato]

i m using commitlint. I find the consistency of the commit messages pretty helpful.

[AhmedMostafa-szjl]

in general, I like the ( Code Review ) videos even if it is an hour-long