Analysis of subviews and form reuse in Laravel5 framework

This article mainly introduces the use of subviews and form reuse in the Laravel5 framework. It is very detailed and comprehensive. It is very helpful for everyone to master the Laravel5 framework. Friends who need it can refer to it

We need to deal with the issue of editing articles. Of course we can add new routes manually, like this:

Route::get('/articles/{id}/edit', 'ArticleController@edit');

Let us use artisan’s route:list on the command line to view our current routes:

php artisan route:list

In line with RESTful In this case, it may be a good choice to directly use laravel's resource route. Then we will remove all the routes and only add the only one:

Route::resource('articles', 'ArticlesController');

Use php artisan route:list again to view the route, wow , a bunch of routes that meet our expectations are generated. Look at each item carefully.

Now add method in controller:

  public function edit($id) {
    $article = Article::findOrFail($id);

    return view('articles.edit', compact('article'));
  }

Now create view

@extends('layout')

@section('content')
  <h1>Edit: {!! $article->title !!} </h1>

  <hr/>

  ...

Okay, I admit that these codes were copied from create.blade.php and modified a bit. The question is do we need to repeat them? We will deal with this issue later, now let’s look at the form submission issue. In the routing, php artisan route:list, read it again, the modification uses the PATCH method, let's modify the view:

{!! Form::open(['method' => 'PATCH', 'url' => 'articles/' . $article->id]) !!}

Visit /articles/1/edit in the browser, check the source code, and find laravel The hidden field of _method=PATCH is automatically generated.

The first problem is that we edit the article, but the article information is not displayed. Let's modify the view:

 {!! Form::model($article, ['method' => 'PATCH', 'url' => 'articles/' . $article->id]) !!}

OK, everything's ok, except that the published_on field is still set to the current date, and then We'll handle it.

Now add the method in the controller:

  public function update($id, \Illuminate\Http\Request $request) {
    $article = Article::findOrFail($id);
    $article->update($request->all());

    return redirect('articles');
  }

We also need to verify during the modification process, let us reuse our Request class, rename CreateArticleRequest to the more general ArticleRequest, and don’t forget to modify the parameters in the store method.

  public function update($id, Requests\ArticleRequest $request) {
    $article = Article::findOrFail($id);
    $article->update($request->all());

    return redirect('articles');
  }

The remaining problem now is that our new and edit use most of the same code, such as displaying errors, but they exist in two copies, let's Modify this question.

We create a new file list.blade.php directly under views/articles, and copy the error handling code from create.blade.php:

@if ($errors->any())
  <ul class="alert alert-danger">
    @foreach($errors->all() as $error)
      <li>{{ $error }}</li>
    @endforeach
  </ul>
@endif

In create.blade.php, just replace the error handling code with the following statement:

@include('articles.list')

Let's deal with the form code again. The form code is different except that the form is different from the submit button. , others are almost the same. We create a view articles/form_partial.blade.php and copy the code

<p class="form-group">
  {!! Form::label(&#39;title&#39;, &#39;Title:&#39;) !!}
  {!! Form::text(&#39;title&#39;, null, [&#39;class&#39; => &#39;form-control&#39;]) !!}
</p>

<p class="form-group">
  {!! Form::label(&#39;body&#39;, &#39;Body:&#39;) !!}
  {!! Form::textarea(&#39;body&#39;, null, [&#39;class&#39; => &#39;form-control&#39;]) !!}
</p>

<p class="form-group">
  {!! Form::label(&#39;published_at&#39;, &#39;Publish On:&#39;) !!}
  {!! Form::input(&#39;date&#39;, &#39;published_at&#39;, date(&#39;Y-m-d&#39;), [&#39;class&#39; => &#39;form-control&#39;]) !!}
</p>

<p class="form-group">
  {{--这里要设置变量，依据是编辑还是修改来改变，当然也可以不放置在partial中--}}
  {!! Form::submit($submitButtonText, [&#39;class&#39; => &#39;btn btn-primary form-control&#39;]) !!}
</p>

Modify create.blade.php

@extends('layout')

@section('content')
  
Write a New Article

  


  @include('articles.list')

  {{--使用我们添加的 illuminate\html 开源库--}}
  {!! Form::open(['url' => 'articles']) !!}
    @include('articles.form_partial', ['submitButtonText' => 'Add Article'])
  {!! Form::close() !!}

@stop

Modify edit.blade.php

@extends('layout')

@section('content')
  
Edit: {!! $article->title !!} 

  


  @include('articles.list')
  {{--使用我们添加的 illuminate\html 开源库--}}
  {!! Form::model($article, ['method' => 'PATCH', 'url' => 'articles/' . $article->id]) !!}
  @include('articles.form_partial', ['submitButtonText' => 'Update Article'])

  {!! Form::close() !!}

@stop

The above is the entire content of this article, I hope it will be helpful to everyone’s study , please pay attention to the PHP Chinese website for more related content!

Related recommendations:

Pages and Form Validation of Laravel 4

About Laravel framework database CURD operations and coherent operations Analysis

About the method of PHP framework Laravel plug-in Pagination to implement custom paging

The above is the detailed content of Analysis of subviews and form reuse in Laravel5 framework. For more information, please follow other related articles on the PHP Chinese website!