Faker VS Laravel-From-Scratch-Blog-Project

A brief explanation of my use case; I'm working on a project where part of it is a random person generator. Users can select a language, gender and birthday range and it'll spit out X amount of random people. This was based on FakerPHP but had a few issues, which I outlined in the initial post.

Part of this is the drivers. A few months ago I added a "random driver generator", where users can select a language, gender, and birthdate range to generate a specified amount of random drivers using Faker.

Makanya pake FakerPHP

Factories are stored in the database/factories directory. This directory by default contains a file UserFactory.php which defines the UserFactory class. Every factory class has a method definition() that returns a set of model attributes with default values as fake data. Laravel uses Faker PHP library to generate dummy data.

Deprecate property access - https://github.com/FakerPHP/Faker/pull/164

Faker

This post is a part of the Week X of 100DaysOfCode Laravel Challenge series. We are building the Blog project while following the Laravel 8 from Scratch series on Laracasts with the 100DaysOfCode challenge.

Update Blog project. Replace the database/seeders/DatabaseSeeder.php class run() method content with the above code and run the following command.

On the blog listing page of our Blog Project, we have N blog posts and behind the scenes Laravel runs N+1 queries to fetch those posts and their categories. The first query fetches posts and the rest fetch the category for each post.

To see the full changelog of this episode added to the Blog Project, see the GitHub commit Ep#25 Show All Posts Associated With a Category .

Our next goal is to assign a category to our blog posts in our Blog Project. We show the category name on the blog archive and single post pages under post title.

At this point in our Blog Project, we capture the post ID in the route definition for a single post, pass it to the callback function as paramere, and then send it to the findOrFail() method of our Post model.

Contributed to the Blog Project on GitHub.

In our Blog project we have Blade templates for our Blog posts views. The view for the Blog listing page is posts.blade.php and for individual post is post.blade.php. These files contain full HTML structure from the tag to , to , and to tag, the full HTML structure. This approach is bad because it poses duplication in files and if you need to a add a change like including a new CSS file, you will have to change all files to add that change. There are two ways to mitigate this problem in Laravel.

I already have been working in Laravel for some time but I wanted to go through all of the Laravel concepts from scratch, to enhance my knowledge and experience. I chose the Laracasts Laravel 8 from scratch series to follow along the #100DaysOfCode. The outcome of the course will be a working Blog project. I created a blank Laravel project and pushed it to Github. As we follow the course, we will turn this blank project into a working Blog.

Move post finding logic from route def to a Model class