You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"diff-cover" is a great project. I have a small suggestion:
the current report display is single-page, and when there is a large amount of incremental code,
having too many files on one page makes it difficult to view.
I would like to ask if there are plans to optimize the report display,
similar to projects like "gcovr" or "reportgenerator," which offer improved report visualization.
The text was updated successfully, but these errors were encountered:
Its a good idea. There are no plans to do it right now. I maintain this project in that I keep it up to date as python and the project dependencies evolve and I manage contributions others make.
I also look into issues when the person provides enough detail where I think I can help.
But I dont really add features of my own to the project very often anymore.
I understand that readability on the user interface level is an engineering challenge.
Diff-cover places a stronger emphasis on the coverage mapping of incremental code changes rather than presentation.
Therefore,
what I am contemplating is whether any subsequent individuals who work on diff-cover could integrate new feature optimizations,
such as enhanced report presentation, into upcoming releases of diff-cover.
"diff-cover" is a great project. I have a small suggestion:
the current report display is single-page, and when there is a large amount of incremental code,
having too many files on one page makes it difficult to view.
I would like to ask if there are plans to optimize the report display,
similar to projects like "gcovr" or "reportgenerator," which offer improved report visualization.
The text was updated successfully, but these errors were encountered: