survey: -allow-errors does not name the failed packages in Markdown
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- go, markdown
- Domain
- cli, developer-experience
Research direction
Start with the Markdown Checks table and the -allow-errors output path; compare it with checks.typeCheck.failed in the JSON output to see where failed package names are available. Check README.md:1504 and skills/declscope-adoption/SKILL.md:173 for the promised behavior. Done when Markdown identifies failed packages or both docs accurately direct users to JSON.
Written by the indexing model from the issue text.
Description
README.md:1504 and skills/declscope-adoption/SKILL.md:173 say that -allow-errors "names it under type check". The Markdown row only counts, as in 0 packages ok, 1 failed, and nothing is printed on stderr. Only checks.typeCheck.failed in the JSON names the packages. It has been this way since #98.
Markdown is the default format, so it never tells you which package failed.
Suggested fix
List the failed packages under the Checks table in Markdown, which is what the docs promise. Or correct both documents to point to the JSON.
- Dominant language
- Go
- Stars
- 42
- Forks
- 1
- Avg merge
- 1h 18m
- Merged PRs (30d)
- 94
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from mpyw/declscope
-
documentation P3
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
documentation P3
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
bug P2
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
bug P2
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
Similar issues
-
🕷️ bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
sysadminsmedia/homebox#1805 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
router-for-me/CLIProxyAPI#6851 ·
Maintainers usually reply within 1 day
-
usage: a custom provider's balance meters ("…%" in the balance path) ignore the Left/Used switchOpen
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
[bug]: docs: Update webhook delete examples to use the correct flag (--webhook-id)Possibly taken @MuhammadHassan968 claimed this today. Openbug
Difficulty 1/5 Under an hour Newbie friendliness 84/100
goharbor/harbor-cli#1127 ·
Maintainers usually reply within 12 days