Respect output format option
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.5k
- Forks
- 228
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 48
Description
Is your feature request related to a problem? Please describe.
respect logs in CI can be very large and noisy, which increases storage usage and makes results harder to read.
Current formats:
lint:stylish,codeframe,json,checkstyle,codeclimate,summary,markdown,github-actionsscorecard-classic:stylish,jsonstats:stylish,json,markdown
Describe the solution you'd like
-
Add formats to
respectcommands (e.g.codeclimate,github-actions,summary...) -
Add additional CI-friendly format:
junit(JUnit XML) for CI test reports (GitLab / Bitbucket)
https://docs.gitlab.com/ci/testing/unit_test_reports/#junit-xml-format-specification
https://support.atlassian.com/bitbucket-cloud/docs/test-reporting-in-pipelines/
- Optional: if
--formatis not provided, detect CI and pick a better default format.
Describe alternatives you've considered
Additional context
Formats in oxlint: https://oxc.rs/docs/guide/usage/linter/output-formats
Vitest reporters: https://vitest.dev/guide/reporters.html#built-in-reporters
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the format handling for the respect commands and compare the existing lint, scorecard-classic, and stats format lists. Review the linked oxlint and Vitest reporter references, then define support for the requested formats, including JUnit XML; done means the commands accept and produce the documented formats with coverage from the project's relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ci-cd, cli, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100