Rails%203%20In%20Action

The projects API
With this new authorization added you will make a commit, but before that you’ll run
a customary check to make sure everything is still alright by running rake spec,
because all you’ve edited in this section is the API. You should see this output:
47 examples, 0 failures, 19 pending
Great, so let’s go ahead and commit this then:
git add .
git commit -m "Only admins are able to create projects through API"
git push
In the response for your create action, the headers point to a location (you customized)
of a project, something such as http://example.com/api/v1/projects/1. Currently,
this URL doesn’t go anywhere because it needs the show action to exist. You
should probably get on to that.
13.1.8 A single project
You’ve got a link (http://example.com/api/v1/projects/1) provided by your create
action that doesn’t go anywhere if people try to access it. Soon this URL will show a
particular project’s attributes through the show action in your Api::V1::Projects-
Controller. Within those attributes, you’ll also show a last_ticket element, which
will contain the attributes for the most recently updated ticket. To do this, you use
another option of respond_with, the :methods option. Using this option will change
the output of each project resource in your JSON API to something like this:
{
}
"project": {
"created_at": "[timestamp]",
"id": 1,
"name": "Ticketee",
"updated_at": "[timestamp]",
"last_ticket": {
"ticket": {
"asset_updated_at": null,
"created_at": "[timestamp]",
"description": "A ticket, nothing more.",
"id": 1,
"project_id": 1,
"state_id": null,
"title": "A ticket, nothing more.",
"updated_at": "[timestamp]",
"user_id": 2
}
}
}
Using the last_ticket method, people using the API will be able to discover when
the last activity was on the project. You could add other fields such as the comments
too if you wished, but this example is kept simple for quality and training purposes.
365