laravel4cookbook

API 132
1 'Event' => 'Illuminate\Support\Facades\Event',
.
This was extracted from app/config/app.php.
I changed the key of that entry to Events but you can really call it anything you like.
.
It’s often just easier to change the name of the classes you create than it is to alter the aliases array.
There are many Laravel 4 tutorials that will refer to these classes by their alias, so you’ll need to
keep a mental log-book of the aliases you’ve changed and where they might be referred to.
Testing Endpoints
It’s not always easy to test REST API’s simply by using the browser. Often you will need to use an
application to perform the different request methods. Thankfully modern *nix systems already have
the Curl library, which makes these sorts of tests easier.
You can test the index endpoint with the console command:
1 curl http://dev.tutorial-laravel-4-api/event
.
Your host (domain) name will differ based on your own setup.
.
You should only be seeing a JSON response - if you’re seeing HTML there’s a good chance it’s a
Laravel error page. Check your application logs for more details.
Unless you’ve manually populated the event table, or set up a seeder for it; you should see an empty
JSON array. This is a good thing, and also telling of some Laravel 4 magic. Our index() action returns
a collection, but it’s converted to JSON output when passed in a place where a Response is expected.
Let’s add a new event: