The LTTF dashboard is great for a project wide overview and being able to get the exact path of files with lint errors is helpful.
However, when working on or planning work on a vertical slice/business module it's hard to tell what lint rules could be scoped in to work (or possible legacy code that could cause confusion and require extra time to parse and work on even if left alone).
Working on deprecation tooling, I've found it really useful to have a directory tree view to drill down and get more information of errors with directory navigation.
From the LTTF JSON output, this data is all available and parsable (or would only require minimal changes).
Would this be something of interest to add or refactor the dashboard to work with?
The LTTF dashboard is great for a project wide overview and being able to get the exact path of files with lint errors is helpful.
However, when working on or planning work on a vertical slice/business module it's hard to tell what lint rules could be scoped in to work (or possible legacy code that could cause confusion and require extra time to parse and work on even if left alone).
Working on deprecation tooling, I've found it really useful to have a directory tree view to drill down and get more information of errors with directory navigation.
From the LTTF JSON output, this data is all available and parsable (or would only require minimal changes).
Would this be something of interest to add or refactor the dashboard to work with?
Below is an example screenshot from https://github.com/rtablada/ember-project-deprecation-dashboard which has a different purpose/data structure, but was heavily influenced by LTTF and was built to visualize this directory level information.