Skip to content

fix: report output format failures as usage errors - #363

Open
codeforester wants to merge 2 commits into
mainfrom
bug/343-20260918-output-format-errors
Open

codeforester wants to merge 2 commits into
mainfrom
bug/343-20260918-output-format-errors

Conversation

@codeforester

Copy link
Copy Markdown
Contributor

Summary

  • Classify public OutputFormatError failures at the run_app process boundary as exit-code 2 usage errors.
  • Preserve safe actionable dependency/format messages in human output and use output_format_error in JSON mode.
  • Add process-boundary tests for optional YAML dependency failures and document the contract.

Closes #343

Validation

  • uv run --extra dev --extra typer --extra quality python -m pytest tests/test_optional_yaml_dependency.py tests/test_json_contracts.py -q
  • Ruff check and format check for changed Python files
  • git diff --check

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.

bug: expose actionable output-format errors at the process boundary

1 participant