Now that we’ve hit feature complete status it’s about getting more of the legwork down to get us really ready for integration. The first necessary feature we need before that is paging. As I wrote earlier, some endpoints don’t need paging and all of them technically have it as an optional thing. However to be really useful we need to have paging for several endpoints like posts, photos, conversations, et cetera. It looks like we can leverage a lot of the way we do paging in the lower levels for streams and just create a standard pager class that the API endpoints that need it can use. I’ve laid out how I want to approach that so now it’s on to implementation.
Along with the progress on the paging there has been progress on other mundane areas. All of these features were developed in side branches which needed to be reviewed and integrated into the main API branch. We are down to one endpoint left before the API branch itself is feature complete, not just having the code. All of the branches are orthogonal except for the routes.rb file and the en.yml messages file so it’s pretty easy integration but needs to be done properly. In the mean time we are also having discussions about the finer grained permission sets that apps will request and users will be notified about. So for example, an app could be given permissions to only read posts but read/write comments on posts, and so on. The endpoints already check for read/write tokens but they are broad tokens. Part of the next steps will be putting in the proper requests and making sure that the information presented to users is clear.
- All but one endpoint is integrated back into the API main branch
- Started work on the API Paging infrastructure
- Looking at the finer grained permissions for each endpoint