Display Reason For Code Flagged - Admin View

[Maillman]

Overview

After taking a little bit of time to figure out why the quality checker flagged some lines in a previous issue (#9). I was thinking that it may be useful for admins to know why the quality checker flags certain lines the way it does.
Perhaps when an admin views a code quality section, they may also see what caused those lines to be flagged, whether it be a sentence or two describing how some checks are performed, or highlighting the offending lines or characters. It could also be done in an entirely different manner. I just think it would be nice for the quality checker to be a little bit more user-friendly.

Student View

My current thought process is to show the reason for code being flagged only to admins, so normal students can't get around the quality check, but there is room for discussion to allow it to be shown to students as well.

[19mdavenport]

Due to the base being checkstyle, I'm not sure how feasible this is. Perhaps you could replace the error messages with something that can be split up by the autograder, but otherwise I'm not sure if this would be doable without forking base checkstyle and depending on the fork rather than the base.

Keep in mind this is technically a program separate from the autograder that the autograder runs, so any mention of student vs. admin should be framed with that included. There have probably been very few students who have run this themselves from the code, but this is a public repository and students could feasibly do so currently (could be changed).

If you wanted to, it would probably not be difficult to make an additional xml file for which checks to run inside the autograder (reference to how base checkstyle does configurable error messages)