Adds fixer outcomes to reporting#41
Draft
NickSdot wants to merge 19 commits into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Console, JSON, perf now report fixes; Checkstyle unchanged.
Depends on #29, #30, #31, #32, #33, #34, #35, #36, #37, #38, #39 and #40.
This PRs diff will shrink as preceding PRs are merged and this branch is rebased.
Diff against previous branch: NickSdot:stack-09-performance...NickSdot:stack-10-reporting (different to diff in here only until the previous branch was merged)
Console Output
Future Scope
While working on this I realised related architectural weakness. Pretty sure you will spot it either here or already in earlier branches. :) I, however, think changing it in here would make the PR explode in scope. For that reason I here focus on the actual report result/output instead of underlying architecture that would touch much of the processing related stuff. Will follow up for the rest in a separate PR.