Once #389 , #390 and #391 are done, we should use these properties in the DiagnosticReport.
Expected behavior
The code should loop over the property classes, compute the scores and use that to create the diagnostic report. All user facing functionality should stay the same with the exception of progress bars.
Similarly to what was done in the QualityReport, we should base the progress bar off of each property and compute the total length based on what the property loops over.
Additional context
The implementation should draw influence from the QualityReport refactoring done in #377 and #378.
amontanez24
commented
1 year ago
Problem Description
Once #389 , #390 and #391 are done, we should use these properties in the DiagnosticReport.
Expected behavior
Additional context