codebright

Build An App 1: Playstation Game Collection 379
1 public function edit(Game $game)
2 {
3 // Show the edit game form.
4 return View::make('edit');
5 }
Our edit form needs to be able to populate the form with default items from our game, so we need
to pass our game instance into the view. Let’s change this now.
1 public function edit(Game $game)
2 {
3 // Show the edit game form.
4 return View::make('edit', compact('game'));
5 }
We have used the compact() method once again to create the view data array. Now it’s time to
handle form submission for the edit form. This is the handleEdit() action as it currently stands.
1 public function handleEdit()
2 {
3 // Handle edit form submission.
4 }
Well that’s a little plain isn’t? I’m fairly sure that comment isn’t going to persist our edited game to
the database. Let’s fill in the blanks. The edit form provides the game’s ID as a hidden field so we
can use that to retrieve the game instance and modify its column values.
1 public function handleEdit()
2 {
3 // Handle edit form submission.
4 $game = Game::findOrFail(Input::get('id'));
5 $game->title = Input::get('title');
6 $game->publisher = Input::get('publisher');
7 $game->complete = Input::has('complete');
8 $game->save();
9
10 return Redirect::action('GamesController@index');
11 }
That’s better! We use the findOrFail() method on the Game class. It’s similar to the find() method,
except that it will trigger an application 404 event if an object with the provided primary key cannot