5 ms·
Considering that the API is you product, getting it documented should probably be you #1 priority. Even a rudimentary documentation, which you can then update l
by troels 12y ago
Considering that the API is you product, getting it documented should probably be you #1 priority. Even a rudimentary documentation, which you can then update later, would be better than none.
- tmornini_ey 12y agoHey there. Yes, agree, thank you, but depends upon how many eyes you want on it along the way. Said another way: didn't realize that today was Hacker News day! :-) We DO have https://api.subledger.com https://api.subledger.com which is Swagger documentation, but we lack a directed HOWTO document that describes double-entry accounting and how our API represents it. Believe me, we're working on it! :-)
- bdcravens 12y agoI've been using Apiary to document some APIs, and it seems pretty easy to add in-line explanation in Markdown.
- tmornini_ey 12y agoThanks, I'll take a look!