https://github.com/memberapp/memberapp.github.io/issues/138
This is on my todo list. API still quite messy and changing quite rapidly atm as I add new features, so would add quite a lo
t of overhead to do it before things have settled down a bit.
In such approach you have two instances of running api V1 - known publicly & frozen, second V2 without doc but used for dev and changes for the time when it becomes mature to document.
Yes,it may be an unnecessary overhead eating U time when things are changing rapidly.Best is to make snapshot & document it as v1 publicly, then do changes in v2 & documented it later.
