`normalize-docs` silently drops the first of two `--input` files
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- Half a day
- Newbie friendliness
- 84/100
Research direction
Read the normalize-docs command in main.py and compare its input option with coverage_matrix.py; the issue says main.py currently passes one input. Then add or inspect a command level test for repeated --input values. Done means both paths reach validation and living-doc normalize-docs --input=a --input=b --output=o exits 1.
Written by the indexing model from the issue text.
Description
Description of Technical Debt
living-doc-utilities docs/contracts/pipeline-rules.md § One project, one pipeline, one documentation source: two
documentation files in one run fail with MULTIPLE_DOCUMENTATION_SOURCES. coverage-matrix takes --doc-input
more than once for exactly this reason. normalize-docs declares one --input, so click keeps the last, a second
file never reaches validate_inputs, and the command exits 0. The action cannot reach it (main.py passes one input);
a hand-written CLI call can.
Impact of Technical Debt
- A CLI user loses a documentation file without any error.
Category
Code Quality / Refactoring
Priority
Medium - Should be addressed soon
Proposed Solution
--input takes multiple=True and passes every path to the validation, as coverage_matrix.py does, with a test through the command.
Effort Estimate
Half a day
Dependencies / Related
No response
Additional Context
Measured 2026-11-12 at living-doc-toolkit fea9aa6 (v0.1.0). Re-check:
living-doc normalize-docs --input=a --input=b --output=o exits 1 when fixed.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 19
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from AbsaOSS/living-doc-toolkit
-
tech debt
Difficulty 1/5 Under an hour Newbie friendliness 88/100
AbsaOSS/living-doc-toolkit#120 ·
Maintainers usually reply within 1 day
-
tech debt
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
AbsaOSS/living-doc-toolkit#116 ·
Maintainers usually reply within 1 day
-
tech debt
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
AbsaOSS/living-doc-toolkit#115 ·
Maintainers usually reply within 1 day
-
tech debt
Difficulty 4/5 1-2 days Newbie friendliness 55/100
AbsaOSS/living-doc-toolkit#119 ·
Maintainers usually reply within 1 day
-
tech debt
Difficulty 5/5 Over a week Newbie friendliness 25/100
AbsaOSS/living-doc-toolkit#117 ·
Maintainers usually reply within 1 day
All issues in AbsaOSS/living-doc-toolkit
Similar issues
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
JheysonJhordyHuarauyaRiquelme/sprocguard#18 ·
Maintainers usually reply within 1 day
-
enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
dlq/synthpopcan#59 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
mdn/translated-content#40220 ·
Maintainers usually reply within 4 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
ETSInitiative/PETSIRD#243 ·
Maintainers usually reply within 1 day
-
deferred p2
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
cuadrao-ai/argus#2160 ·
Maintainers usually reply within 1 day