com
com copied to clipboard
What else for 1.0?
Besides stable APIs, solid docs, and more test coverage ... what else should we focus on for a 1.0 release? Also, where can the docs be improved? Where are there questionable API choices?
I'm putting a deadline of Feb 1 on the 1.0 milestone. That gives a timeline constraint. Hopefully we use it enough in that time to know what a solid 1.0 API looks like.
Jeff, have you seen the dependency injection framework from uber- https://github.com/uber-go/fx Do you see think it would be a useful pattern or library in com?