5 ms·
Do you do API versioning at taskrabbit?
by jsnk 13y ago
Do you do API versioning at taskrabbit?
- aantix 13y agoTake a look at VersionCake ( https://github.com/bwillis/versioncake https://github.com/bwillis/versioncake ). Yes, I am one of the authors. After having gone down the path of separate API controllers, we learned that the APIs had become a second class citizen and had different code paths than the web based resources. We unified everything; the same endpoint that the user goes through for web signup is the same endpoint that the API will request for a create. We're just using respond_to's to respond to the various types of clients that make requests. Utilizing Rails, Jbuilder, and VersioCake, we have a unified, versioned API that can support earlier client versions (thanks to VersionCake).
- killion 13y agoThat's a really great use of jbuilder. I thought their only benefit was separating view logic but this really makes them useful. Now if they only had a name that was different from a Java thing.
- bleonard 13y agoYes, there's some fancy business for point release semantic versioning, but something I left out was that the backend API engines all have EVEN MORE directories: apps/account/controllers/account/v3/something_controller.rb That kind of thing.