Method to check if current request is a POST request.

[ghost]

This is much more useful than using Request::method() when updating models. If the request is a POST request, update your model with the input, otherwise render to response.

[franzliedke]

How about just return $method == 'POST'?

[midned]

I'm fast haha

[midned]

I don't really agree with this... There's no much use for checking if the method is a specific one. And if this method is added then must be added is_get is_put and is_delete too.

[ghost]

It makes life a little easier with these methods.

    public function action_edit($id)
    {
        $post = Post::find($id);

        if(Request::is_post())
        {
            $post->fill(
                'title' => Input::get('title'),
                'content' => Input::get('post')
            );

            $post->save();
        }

        return View::make('post.edit')->with('post', $post);
    }

[midned]

I think you should use RESTful controllers. Use different methods to separate the logic in your code.

[ghost]

I feel these should only be used if your intentions are to use all of the RESTful methods. You could also get some code duplication by being restricted to using a RESTful controller.

[franzliedke]

Also, read about POST-redirect-GET.

[midned]

@franzliedke 👍

[ghost]

This is how I have always written my applications in Laravel (with POST-redirect-GET) and I do see how without it there could be issues.