Use with only a subset of controllers?

[ileitch]

My API is contained within a larger Rails app. They all inherit from a common parent class, so I can easily change them to use ActionController::API, however I'm unsure what to do about the Rails::ApiApplication setup step?

Cheers

[spastorino]

We are going to add a config.api_only! option inside config/application.rb so if you add this config middleware stack will be reduced and if not you keep previous state. After that you will be able to just inherit from ActionController::API. Anyway I'm interested in seeing if that worth, I mean how much that improves. If you can measure it and share results :).
Thanks for helping.

Ahh another thing, there's no Rails::ApiApplication anymore, the README is fixed now.

[carlosantoniodasilva]

The idea behing the config is that it will reduce your middleware stack and reconfigure some generators to not generate stuff like templates and assets - css/js. In case of shared apps, this option cannot be used because you'll lose features like session/cookies, which are required for the non-api part of your app. So the best usage in this case is inheriting from ActionController::API only, and ignore the config.

(of course this is not possible right now because everything is happening inside normal Rails::Application class, there's no config yet).

[ileitch]

OK, so I got my API working by just using ActionController::API, but is this giving much benefit? Isn't the removal the main advantage of this plugin?

[carlosantoniodasilva]

You're getting the benefit of having a smaller set of features in your controllers that handle the API part of your app, which should give you some improvement, but the middleware stack stays the same, so yeah no gain on that side.

We can't say for sure the real gain on this scenario, perhaps you can help us measuring this :). Thanks.

[spastorino]

@ileitch can you check this out?, thanks!