feat: NewsDOM JSON 검증 및 순수 텍스트 추출 도구 추가#273
Conversation
- `tools/validate_dom.py`: Pydantic 스키마(`ParseResponse`) 기반으로 파싱된 JSON 결과물 검증 기능 구현 (`--recursive` 옵션 지원) - `tools/extract_text.py`: 파싱된 NewsDOM JSON 결과물에서 Markdown 포맷팅 등 부가 정보 없이 순수 텍스트만 추출 기능 구현 - `tests/test_tools_validate_dom.py`, `tests/test_tools_extract_text.py`: 신규 도구들에 대한 단위 테스트 추가 (커버리지 100% 달성) - `CHANGELOG.md` 업데이트
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
OpenCode Review Overview
Pull request overviewOpenCode reviewed the current-head bounded evidence and found no blocking issues. FindingsNo blocking findings. SummaryApproval sufficiency: bounded evidence supplied affirmative approval evidence for changed files, coverage/docstring posture, risk surfaces, and current-head verification; approval is not based merely on the absence of known blockers.
Changed-File Evidence Mapflowchart LR
PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
Evidence --> S1["Changed file (7 files)"]
S1 --> I1["repository behavior"]
I1 --> R1["Review risk: Changed file (7 files)"]
R1 --> V1["required checks"]
Evidence --> S2["Test (7 files)"]
S2 --> I2["regression suite"]
I2 --> R2["Review risk: Test (7 files)"]
R2 --> V2["targeted test run"]
|
![opencode-agent[bot]](https://avatars.githubusercontent.com/in/1549082?s=60&v=4){kind=small}
There was a problem hiding this comment.
Pull request overview
OpenCode reviewed the current-head bounded evidence and found no blocking issues.
Findings
No blocking findings.
Summary
Approval sufficiency: bounded evidence supplied affirmative approval evidence for changed files, coverage/docstring posture, risk surfaces, and current-head verification; approval is not based merely on the absence of known blockers.
Verification posture: CodeGraph evidence was initialized and bounded current-head evidence reviewed for changed-file evidence including CHANGELOG.md, src/newsdom_api/synthetic.py, tests/test_benchmark_ocr.py, tests/test_derive_private_baseline.py, tests/test_errors.py, and 9 more.
Linter/static: workflow/static review evidence is bounded by the current-head GitHub Checks gate and changed-file evidence.
TDD/regression: coverage execution evidence and focused changed hunks were reviewed from bounded-review-evidence.md.
Coverage: coverage execution evidence reports supported repository test suites passed.
Docstring coverage: coverage execution evidence reports configured repository docstring gates passed or docstring coverage was advisory.
DAG: CodeGraph/source-backed behavior map connects CHANGELOG.md to the affected review, runtime, or workflow path and required checks.
PoC/execution: coverage-evidence job executed on the current head and reported PASS.
DDD/domain: workflow and repository-governance invariants were reviewed against changed files in bounded evidence.
CDD/context: CodeGraph evidence, changed-file history, and focused hunks were reviewed from bounded-review-evidence.md.
Similar issues: changed-file history evidence was reviewed for comparable local precedents.
Claim/concept check: bounded evidence, repository source, current-head workflow evidence, and, where numeric, scientific, statistical, or literature-backed claims are affected, original-paper/formula evidence and parameter-recovery expectations were used for claims.
Standards search: standards and external-source checks are delegated to configured OpenCode web_search/Context7/DeepWiki sources when applicable; no evidence-backed standards blocker is present in bounded evidence.
Compatibility/convention: changed workflow/script conventions, object naming, and reserved-word safety for schema/API/config/code surfaces were checked in bounded evidence.
Breaking-change/backcompat: deployment evidence and changed-file history were checked for backward-compatibility risk.
Performance: changed surfaces were checked for performance risk in bounded evidence.
Developer experience: changed automation, review, test, setup, and maintenance surfaces were checked for helpful or obstructive DX impact in bounded evidence.
User experience: connected user, operator, API, CLI, documentation, review-comment, status-check, rendering, and workflow-reader behavior was checked for contradictions against code, docs, and tests in bounded evidence.
Visual/DOM: Playwright visual, DOM locator, ARIA snapshot, console, and responsive evidence were checked when a web UI surface was present; for non-web surfaces, API/CLI/log/docs/workflow interaction evidence was reviewed instead.
Accessibility/i18n: accessibility, localization, and human-readable text surfaces were checked where UI, CLI, API message, docs, logs, or review text changed.
Supply-chain/license: dependency, package, model, container, and external-tool changes were checked in bounded evidence.
Packaging: package, build, test, lint, and security contracts were checked in bounded evidence.
Security/privacy: workflow-token, review-gate, and repository-automation security/privacy boundaries were checked in bounded evidence.
- Result: APPROVE
- Reason: New tools added with comprehensive tests and 100% coverage
- Head SHA:
80347dc69d84c7912c597d922dd2efb7dfd88e1e - Workflow run: 28685521804
- Workflow attempt: 1
Changed-File Evidence Map
flowchart LR
PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
Evidence --> S1["Changed file (7 files)"]
S1 --> I1["repository behavior"]
I1 --> R1["Review risk: Changed file (7 files)"]
R1 --> V1["required checks"]
Evidence --> S2["Test (7 files)"]
S2 --> I2["regression suite"]
I2 --> R2["Review risk: Test (7 files)"]
R2 --> V2["targeted test run"]
1 participant
What (구현 내용)
ParseResponse)를 준수하는지 검증하는tools/validate_dom.py도구 추가 (재귀 디렉터리 순회 지원).tools/extract_text.py도구 추가.tests/test_tools_validate_dom.py,tests/test_tools_extract_text.py).Why (해결하는 문제)
Impact (성능/영향)
model_validate를 직접 사용하여 JSON 검증 시 오버헤드를 최소화하고 빠른 오류 반환을 보장합니다.Measurement (측정/검증 방법)
uv run pytest --cov=tools --cov-branch --cov-report=term-missing --cov-fail-under=100을 통해 100% 분기 커버리지 검증 완료.ruff린팅 및 포맷팅 검증(uv run ruff check,uv run ruff format) 통과.PR created automatically by Jules for task 18346969340931316852 started by @seonghobae