This pull request adds a field to the package website main page which tells the user how many packages currently require maintenance. Any package which fails to build, has failing tests, or is without documentation or tags counts towards this total. By clicking a link within this field, the user can filter the table so that only packages with outstanding maintenance are displayed, sorted by the maintenance required.
This functionality was implemented by adding a new (invisble) column to the packages table containing the "todo value" of that row. The "todo value" is an integer representing what kind of maintenance is required on that package.
0: No maintenance required
1: No tags
2: No docs
3: Failing tests
4: Package fails to build.
The table is then sorted and filtered based on this predicate.
All of the new front-end functionality has been tested, but I wasn't able to get the backend HTML generation working on my machine. If there are any errors in this pull request, they're most likely in src/site.rkt.
This is what the page looks like after a fresh reload:
Here it is after the user clicks the "show todos" link:
This pull request adds a field to the package website main page which tells the user how many packages currently require maintenance. Any package which fails to build, has failing tests, or is without documentation or tags counts towards this total. By clicking a link within this field, the user can filter the table so that only packages with outstanding maintenance are displayed, sorted by the maintenance required.
This functionality was implemented by adding a new (invisble) column to the packages table containing the "todo value" of that row. The "todo value" is an integer representing what kind of maintenance is required on that package.
The table is then sorted and filtered based on this predicate.
All of the new front-end functionality has been tested, but I wasn't able to get the backend HTML generation working on my machine. If there are any errors in this pull request, they're most likely in
src/site.rkt.This is what the page looks like after a fresh reload:
Here it is after the user clicks the "show todos" link:
Here you can view a short demo that I recorded demonstrating the new functionality.