Skip to content

🎨 Palette: 빈 디렉토리 이름에 대한 Fallback 제공을 통한 접근성 향상 - #182

Closed
seonghobae wants to merge 4 commits into
masterfrom
palette/empty-dir-name-fallback-15344805252248442131
Closed

🎨 Palette: 빈 디렉토리 이름에 대한 Fallback 제공을 통한 접근성 향상#182
seonghobae wants to merge 4 commits into
masterfrom
palette/empty-dir-name-fallback-15344805252248442131

Conversation

@seonghobae

Copy link
Copy Markdown
Collaborator

💡 What: 루트 디렉토리 생성 시 발생하는 빈 <title><h1>을 방지하기 위해 절대 경로를 fallback으로 사용하도록 수정했습니다 (name.ifEmpty { absolutePath }).
🎯 Why: 시스템 루트 디렉토리는 getName() 호출 시 빈 문자열을 반환하여 스크린 리더 사용자가 해당 페이지의 목적을 파악할 수 없게 만드는 접근성 문제를 해결합니다.
📸 Before/After: 해당 없음 (시맨틱/스크린 리더 개선).
♿ Accessibility: 비어 있던 주요 HTML 시맨틱 태그(title, h1)가 적절한 경로 정보로 채워져 문서 구조를 명확하게 합니다.


PR created automatically by Jules for task 15344805252248442131 started by @seonghobae

루트 디렉토리(`/` 또는 `C:\`)와 같이 `.getName()`이 빈 문자열을 반환하는 디렉토리에 대해 HTML 생성 시 절대 경로(`absolutePath`)를 fallback으로 사용하도록 수정하여 스크린 리더 접근성을 향상시킵니다.
@google-labs-jules

Copy link
Copy Markdown

👋 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 @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

루트 디렉토리(`/` 또는 `C:\`)와 같이 `.getName()`이 빈 문자열을 반환하는 디렉토리에 대해 HTML 생성 시 절대 경로(`absolutePath`)를 fallback으로 사용하도록 수정하여 스크린 리더 접근성을 향상시킵니다.
또한 opencode-review 정책에 따라, 수정된 HTML 출력(title, h1)을 검증하도록 기존 테스트(MainTest.kt)를 업데이트했습니다.
루트 디렉토리(`/` 또는 `C:\`)와 같이 `.getName()`이 빈 문자열을 반환하는 디렉토리에 대해 HTML 생성 시 절대 경로(`absolutePath`)를 fallback으로 사용하도록 수정하여 스크린 리더 접근성을 향상시킵니다.
또한 opencode-review의 적대적(adversarial) 검증 정책을 통과하기 위해, `testProcessDir()`와 `testGoEmptyDir()`을 포함한 모든 연관 테스트 코드에 수정된 `<title>`과 `<h1>` 검증 로직을 추가했습니다.
빌드 디렉토리를 오염시키는 임시 테스트 코드들도 삭제했습니다.
루트 디렉토리(`/` 또는 `C:\`)와 같이 `.getName()`이 빈 문자열을 반환하는 디렉토리에 대해 HTML 생성 시 절대 경로(`absolutePath`)를 fallback으로 사용하도록 수정하여 스크린 리더 접근성을 향상시킵니다.
또한 opencode-review의 적대적(adversarial) 검증 정책을 통과하기 위해, 관련된 모든 단위 테스트(MainTest.kt 내 6개 함수)에 수정된 `<title>`과 `<h1>` 검증 로직을 철저하게 추가했습니다.

@opencode-agentopencode-agentBot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

  • Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

  • Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

  • Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

  • Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

  • Result: REQUEST_CHANGES

  • Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head 51073c861d0670dc55994068c4ad4b442d928875.

  • Head SHA: 51073c861d0670dc55994068c4ad4b442d928875

  • Workflow run: 30424175574

  • Workflow attempt: 1

Coverage evidence

Coverage evidence job did not run or did not publish coverage evidence.

Changed-File Evidence Map

flowchart LR
PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
Evidence --> S1["Changed file (3 files)"]
S1 --> I1["repository behavior"]
I1 --> R1["Review risk: Changed file (3 files)"]
R1 --> V1["required checks"]
Loading

@opencode-agent

Copy link
Copy Markdown

OpenCode Review Overview

  • Head SHA: 51073c861d0670dc55994068c4ad4b442d928875
  • Workflow run: 30424175574
  • Workflow attempt: 1
  • Gate result: REQUEST_CHANGES (approval step)

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

  • Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

  • Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

  • Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

  • Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

  • Result: REQUEST_CHANGES

  • Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head 51073c861d0670dc55994068c4ad4b442d928875.

  • Head SHA: 51073c861d0670dc55994068c4ad4b442d928875

  • Workflow run: 30424175574

  • Workflow attempt: 1

Coverage evidence

Coverage evidence job did not run or did not publish coverage evidence.

Changed-File Evidence Map

flowchart LR
PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
Evidence --> S1["Changed file (3 files)"]
S1 --> I1["repository behavior"]
I1 --> R1["Review risk: Changed file (3 files)"]
R1 --> V1["required checks"]
Loading

@seonghobaeChatGPT Codex Connector

Copy link
Copy Markdown
CollaboratorAuthor

Closing as superseded by draft canonical #364. The same name.ifEmpty { absolutePath } intent is retained there, but #364 is deliberately blocked until it is rebuilt after #363, centralizes one escaped display label, verifies root and ordinary generated pages, adds APA 7 doctoring and changelog, and passes fresh exact-head checks plus independent approval. No evidence from this duplicate head is reused.

@google-labs-jules

Copy link
Copy Markdown

Closing as superseded by draft canonical #364. The same name.ifEmpty { absolutePath } intent is retained there, but #364 is deliberately blocked until it is rebuilt after #363, centralizes one escaped display label, verifies root and ordinary generated pages, adds APA 7 doctoring and changelog, and passes fresh exact-head checks plus independent approval. No evidence from this duplicate head is reused.

Understood. Acknowledging that this work is superseded by #364 and stopping work on this task.

Sign up for freeto 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.

1 participant

@seonghobae