Modify PyTA report messages

[rachelzUT]

Proposed Changes

Edited the PythonTA reports (plain text and HTML) to not show sections with no errors and only show 'good job' message once when there are no errors in either section. This eliminates repeated messages, allowing for a simpler and clearer report. Additionally edited the 'good job' message to include a random emoji.

...

Screenshots of your changes (if applicable)

Type of Change

Type	Applies?
🚨 Breaking change (fix or feature that would cause existing functionality to change)
✨ New feature (non-breaking change that adds functionality)	X
🐛 Bug fix (non-breaking change that fixes an issue)
♻️ Refactoring (internal change to codebase, without changing functionality)
🚦 Test update (change that only adds or modifies tests)
📚 Documentation update (change that only updates documentation)
📦 Dependency update (change that updates a dependency)
🔧 Internal (change that only affects developers or continuous integration)

Checklist

Before opening your pull request:

• I have performed a self-review of my changes.
  • Check that all changed files included in this pull request are intentional changes.
  • Check that all changes are relevant to the purpose of this pull request, as described above.
• I have added tests for my changes, if applicable.
  • This is required for all bug fixes and new features.
• I have updated the project documentation, if applicable.
  • This is required for new features.
• I have updated the project Changelog (this is required for all changes).
• If this is my first contribution, I have added myself to the list of contributors.

After opening your pull request:

• I have verified that the CI tests have passed.
• I have reviewed the test coverage changes reported by Coveralls.
• I have requested a review from a project maintainer.

Questions and Comments

column-gap was added to .main-grid in stylesheet.css for aesthetic purposes, otherwise the title/table of contents and errors sections are spaced together quite closely.

Example of PyTA HTML report with no errors:

Example of PyTA plaintext report with no errors:

[coveralls]

Coverage Report for CI Build 27581017533

Coverage increased (+0.002%) to 90.931%

Details

• Coverage increased (+0.002%) from the base build.
• Patch coverage: 13 of 13 lines across 2 files are fully covered (100%).
• No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.

---

Coverage Stats

Relevant Lines:	4058
Covered Lines:	3690
Line Coverage:	90.93%
Coverage Strength:	17.67 hits per line

---

💛 - Coveralls

[david-yz-liu]

@rachelzUT in addition to the inline comments I left, please also include a screenshot of the updated plaintext report

[david-yz-liu]

Keep properties in alphabetical order

[david-yz-liu]

keep properties in alphabetical order

[david-yz-liu]

As this is shared across the multiple reporters, define this and the no_err_message method in the base PythonTaReporter class

[david-yz-liu]

We need to also display this message if level == "error" and there are no code messages, even when there are style messages. (This is also true of the HTML Reporter, so please double-check that.)

[rachelzUT]

I made this change to plain_reporter.py. For the HTML reporter, the level argument doesn't appear to actually be utilized or affect the output, since the report is produced by display_messages which doesn't even accept level as an argument.

pyta/packages/python-ta/src/python_ta/reporters/html_reporter.py

Lines 55 to 60 in 39191ca

	def print_messages(self, level="all"):
	"""Do nothing to print messages, since all are displayed in a single HTML file."""
	def display_messages(self, layout: BaseLayout) -> None:
	"""Hook for displaying the messages of the reporter

[david-yz-liu]

Nice work, @rachelzUT!