Skip to content

Cleanup JSON and LSP reporter output - #1419

Open
PraneethS42 wants to merge 2 commits into
pyta-uoft:masterfrom
PraneethS42:json-output-change
Open

PraneethS42 wants to merge 2 commits into
pyta-uoft:masterfrom
PraneethS42:json-output-change

Conversation

@PraneethS42

@PraneethS42 PraneethS42 commented Oct 20, 2026 •

Copy link
Copy Markdown
Contributor

Proposed Changes

Moves upload status messages to stderr so that JSONReporter and LSPReporter emit only valid JSON to stdout. No changes were made to either reporter. Also, within configuration.md, changes the available reporter count from 4 to 5 (previous mistake I believe).

Screenshots of your changes (if applicable)

Type of Change

(Write an X or a brief description next to the type or types that best describe your changes.)

Type Applies?
🚨 Breaking change (fix or feature that would cause existing functionality to change)
✨ New feature (non-breaking change that adds functionality)
🐛 Bug fix (non-breaking change that fixes an issue) x
♻️ 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

(Complete each of the following items for your pull request. Indicate that you have completed an item by changing the [ ] into a [x] in the raw text, or by clicking on the checkbox in the rendered description on GitHub.)

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

(Include any questions or comments you have regarding your changes.)

@coveralls

coveralls commented Oct 20, 2026 •

Copy link
Copy Markdown
Collaborator

Coverage Report for CI Build 39527045040

Coverage increased (+0.006%) to 91.593%

Details

  • Coverage increased (+0.006%) from the base build.
  • Patch coverage: 21 of 21 lines across 1 file are fully covered (100%).
  • No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.


Coverage Stats

Coverage Status
Relevant Lines: 4175
Covered Lines: 3824
Line Coverage: 91.59%
Coverage Strength: 21.25 hits per line

💛 - Coveralls

@PraneethS42 PraneethS42 changed the title Output redirection Cleanup JSON and LSP reporter output Oct 21, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants