infoxtractor/src/ix/pipeline
Dirk Riemann 703da9035e
All checks were successful
tests / test (push) Successful in 2m1s
tests / test (pull_request) Successful in 1m18s
feat(use-cases): add inline use-case definitions
Adds RequestIX.use_case_inline so callers can define ad-hoc extraction
schemas in the request itself, bypassing the backend registry. The
pipeline builds a fresh (Request, Response) Pydantic class pair per
call via ix.use_cases.inline.build_use_case_classes; structural errors
(dup field, bad identifier, choices-on-non-str, empty fields) raise
IX_001_001 to match the registry-miss path. Inline wins when both
use_case and use_case_inline are set. Existing REST callers see no
behavioural change.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-18 21:01:27 +02:00
..
__init__.py feat(pipeline): Step ABC + Pipeline runner + Timer (spec §3, §4) 2026-04-18 11:06:46 +02:00
genai_step.py feat(pipeline): GenAIStep — LLM call + provenance mapping (spec §6.3, §7, §9.2) 2026-04-18 11:18:44 +02:00
ocr_step.py feat(ocr): SuryaOCRClient — real OCR backend (spec §6.2) 2026-04-18 12:04:19 +02:00
pipeline.py feat(pipeline): Step ABC + Pipeline runner + Timer (spec §3, §4) 2026-04-18 11:06:46 +02:00
reliability_step.py feat(pipeline): ReliabilityStep — writes reliability flags (spec §6) 2026-04-18 11:20:18 +02:00
response_handler_step.py feat(pipeline): ResponseHandlerStep — shape-up final payload (spec §8) 2026-04-18 11:21:36 +02:00
setup_step.py feat(use-cases): add inline use-case definitions 2026-04-18 21:01:27 +02:00
step.py feat(pipeline): Step ABC + Pipeline runner + Timer (spec §3, §4) 2026-04-18 11:06:46 +02:00