Release 2.0 Roadmap
Hey @kieranjmartin - Just using this to outline my thoughts about how to actually proceed towards R2.
I want to approach this more incrementally so that we don't end up with one mammoth PR that is hard to ensure is backwards compatible.
I think roughly in order (with each of these being separate PRs)
- [ ] Implement the abstract report sub-feature with ascii renderer #98 (and by collateral damage #80)
- [ ] Convert existing diffdf flow to use the abstract report
- [ ] Add html renderer (#8)
At this point I think release and wait for feedback. Assuming no one comes screaming then:
- [ ] Add markdown renderer (#34)
- [ ] Add rtf renderer (#115)
Then do another release, and then free game for all the other outstanding ticket items.
I'd like to move options to a seperate argument as per #13 as part of this, I think that would be a good 2.0 feature too. Otherwise happy.
Part of me likes the idea of adding extensibility to the function (e.g. I can add/customise tests with my own test functions), but while in principle it's cool I don't know how much value it would actually generate