yield very similar results. Yet the implementation is very different. The former dashboard one is much more efficient, easier to maintain and newer than the collection-report one. The latter was made prior to the dashboard-table and proofs to be complicated to work with, this includes client and server code. I just had a try at implementing #86 in both cases. For collection-report it's twisted and complicated and I'd much rather get rid of that code and unify both cases than do that. Hence this issue. I wont port #86 to collection-report.
In the dashboard, the urls:
{fontbakery.com}/dashboard
and e.g:
{fontbakery.com}/collection-report/CSVSpreadsheet%2Fupstream
yield very similar results. Yet the implementation is very different. The former
dashboard
one is much more efficient, easier to maintain and newer than thecollection-report
one. The latter was made prior to the dashboard-table and proofs to be complicated to work with, this includes client and server code. I just had a try at implementing #86 in both cases. Forcollection-report
it's twisted and complicated and I'd much rather get rid of that code and unify both cases than do that. Hence this issue. I wont port #86 tocollection-report
.