Package tree report

[tim-mitchell]

Is your feature request related to a problem? Please describe. I am generating coverage data for several hundred files with many sub-packages. The filter at the top of the index page is ok for finding things in such a long list, but for trying to figure out what packages need the most attention, it's not great. I thought a package folder structure with stats per package would be handier.

Describe the solution you'd like In addition to the current index file, create a second tree-based index file. It would not need sorting.

Describe alternatives you've considered Generating multiple reports with include filters to specify parts of the codebase to report on at a time. This seemed cumbersome.

Attached is my first hack at getting something going using https://www.jqueryscript.net/table/simple-tree-table.html. The results are ugly but usable.

package_tree.zip