Rails%203%20In%20Action

The projects API
another called project, and then check to see if its text is equal to the name of your
project, which it should be if everything works out fine. When you run bin/rspec
spec/api/v1/projects_spec.rb, this spec will fail:
Diff:
@@ -1,10 +1,2 @@
-
-
-
- [timestamp]
- 1
- Ticketee
- [timestamp]
-
-
+
...
2 examples, 1 failure
The diff here shows that the expected XML is nowhere to be found in the response,
and instead you’re getting back a final line of absolutely nothing. This is because your
Api::V1::BaseController doesn’t yet respond to XML requests. So now with a failing
test you can go right ahead and change this controller to fix it. To make your API serve
XML requests, you’ll change this line in app/controllers/api/v1/base_controller.rb
respond_to :json
to this:
respond_to :json, :xml
This simple little change will now make your spec pass, which you can see by running
bin/rspec spec/api/v1/projects_spec.rb:
2 examples, 0 failures
Apologies if something harder was expected, but it really is this simple in Rails. You’ve
only changed the API controller and spec, and it’s all contained in itself, but even so
it’s still a good habit to run all the features and specs to make sure everything is fine:
61 scenarios (61 passed)
726 steps (726 passed)
# and
36 examples, 0 failures, 12 pending
Green is good. Commit this change:
git add .
git commit -m "Support XML & JSON with /api/v1/projects"
git push
Now that you’ve got your first action of your API responding to both XML and JSON,
why don’t you make some more actions, like the create action for creating projects in
Ticketee?
359