Dealing with releases of single page applications

Re:Dealing with releases of single page applications by swalsh on Friday March 11, 2016 @05:18PM (#11269953)

If this was a problem I was truly concerned about, i'd attack it with discipline and tinkle bit of versioning. If you're making a breaking change to the API perhaps you should increment the major version, and support both, and then sail away the old API when you feel comfortable doing so.

yoursite.com/api/v1/call

yoursite.com/api/v2/call

[ Parent | on HN ]

Re:Dealing with releases of single page applications by hankeypancake on Friday March 11, 2016 @08:43PM (#11270871)

Yes, api versioning would be nice. However, with limited resources (as always) this takes you very far without it. Api versioning also only handles breaking api changes (which this doesn't really protect you from, depending on how the users act to the notification), this also notifies the users to refresh their browsers for hotpatches regarding the frontend, and also regular feature releases. So even if you have api versioning in place, I still see benefits from having this in place

[ Parent | on HN ]

Re:Dealing with releases of single page applications by davidjnelson on Friday March 11, 2016 @09:54PM (#11271130)

Seems like graphql would solve the api versioning problem pretty well.

[ Parent | on HN ]