nextcloud / nextcloud/cookbook
Parser for output of linters
Open
Nobody has claimed this yet.
enhancement
meta and development
- Dominant language
- HTML
- Stars
- 641
- Forks
- 113
- Avg merge
- 21h 31m
- Merged PRs (30d)
- 26
Description
The linters are run. Any warnings are ignored and will be hidden/buried in the logs of the action. One should add parsers for the output of the linters/checkers to generate annotations during the run
This might be relevant to
- php-cs-fixer
- PHP linter
- psalm (not yet)
- eslint
- stylelint
- prettier
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
Locate the GitHub Actions workflow that runs the listed linters and inspect how their warnings are currently logged. Determine the output formats for php-cs-fixer, the PHP linter, eslint, stylelint, and prettier; done means their warnings produce run annotations instead of being hidden in the logs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- eslint, php
- Domain
- ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100