The following tutorial column will introduce you to the method of writing a professional RestfulAPI in Laravel. I hope it will be helpful to friends in need!
Laravel teaches you to simply write professional URLs
Introduction
After we connected to the database and used the migration function to create the database table structure, Used Seeder to initially fill in some dummy data for the database. With these preparations in place, we can consider building a resource interface function to
provide external data support.
Do you feel that the API interface and data you designed are different from those of other major manufacturers? The document data structure provided is different, does not look so professional, or not so standard? How many grades are we still behind Dachang?
Laravel provides a simple and standard way that allows us to follow best practices and write professional URLs.
For example, for resources, use the restful style to declare the url routing address:
The first column is the http request method, and the second column is the declaration in laravel Routing rules, the third column is the corresponding controller method. The resource list above covers all actions of adding, deleting, modifying and checking, which can be said to be very comprehensive.php artisan make:controller EventsController --resource
We use the
–resourceoption to generate all the above methods in the target controller.
The generated file is located in app/Http/Controllers/EventsController.php. The initialization content is as follows:
These methods are true It works right out of the box.
method of the
Route class to register the resource: Route::resource('events', 'EventsController');
view file, use the default layout file, and fill in the following code:
@extends('layouts.app') @section('content') <h1>Events</h1> @endsection
Open the app/Http/Controllers/EventsController file and modify the
index method: public function index(){
return view('events.index');}
use App\Event;
method:
$events = Event::all();return view('events.index')->with('events', $events);
With the above data, simply iterate through the output content in the view , modify the view file as follows: <h1>Events</h1>
@forelse ($events as $event)
In the template file
The method will determine whether the
$eventsvariable has at least one element for traversal, and if not, output@emptyThe content of the block. Access the routing address in the browser, and the output content is roughly as shown below. Because of the fake data filled in by Faker, it looks like this:
If the amount of data is too large, this page will probably take a long time to load. , the list is long. So paging is needed. To add the paging function, the SQL statement used is probably like this:select id, name from events order by id asc limit 10 offset 0; select id, name from events order by id asc limit 10 offset 10;
method on the model:
$events = Events::paginate(10);
Every The page is set to 10 entries. We need to have a navigation bar for the previous page, next page, and page number in the view, and we don't need to write it manually. Laravel actually inherits the Illuminate\Pagination\LengthAwarePaginator class returned by the
paginate method. It is enough to just add this line to the view: {!! $events->links() !!}
You can also use a third-party library to fill in dummy data, and the efficiency is significantly improved. Only when the data is prepared can we talk about business logic and interface docking. This data is also the basis of the application, so it is important.
This article is a supplement to the laravel database migration function described in the previous chapter. Database migration is a relatively large move,
especially for application databases that have been put into production. If it is necessary to update the migration, you need to conduct drills in anticipation to deal with possible emergencies. An accident occurred.
The above is the detailed content of Laravel teaches you to simply write a professional RestfulAPI. For more information, please follow other related articles on the PHP Chinese website!