I’ve pushed this report out on the REST framework mailing list, but it’s relevant here too: https://www.encode.io/reports/may-2018
Essentially, all the functionality that’s being built into the core of API Star - schema validation, docs generation, dynamic client libs, and (eventually) API mocking, is also being built out into a hosted service.
The plan is for the API Star command line tool to provide all that functionality while also providing a service that wraps it all up into a neat package (think something a bit like ReadTheDocs but for APIs)
The complete-server-framework parts of API Star don’t quite fit in so well as the rest of the core functionality, and will need to think about how best to document the different aspects as we go along. It’s possible that part could be split out into a separate package entirely, so that we’ve got something like
apistar (which’ll eventually end up being used by REST framework for it’s API docs, schema generation, and client libs), and the server, as