fix(errors): 재전송이 결과 불명을 푸는지는 백엔드가 보낸 code로 정한다 #25
Closed
donghyeon.kang
wants to merge 0 commits from
donghyeon.kang/fix/r9-refusal-backend-code AGit into main
pull from: donghyeon.kang/fix/r9-refusal-backend-code
merge into: :main
:main
:fix/r9-structure-locale
:fix/r9-adapter-carryover
:test/shared-build-lock-order
:ci/dependency-cache-same-filesystem
:ci/release-tag-for-a11y-review
:ci/merge-dependency-cache
:fix/test-timeouts-measured
:fix/feature-residue-word-boundary
:fix/provider-wait-stderr
:fix/provider-job-host-requirements
:fix/ungated-vitest-spec
:fix/a11y-evidence-routes
:fix/verify-parts-diagnostics
:claude/w2-fe-ci-perf-dce080
:fix/child-process-test-timeouts
:chore/layout-rules-r2-r5
:claude/fe-b-docs-korean-645f55
:chore/ci-merge-jobs
:chore/layout-3-merge
:claude/fe-c-harness-0ae061
:chore/layout-2-sample-removal
:chore/layout-1-cleanup
:docs/review-guide-pointer
:fix/maturity-review-2026-11-06
:fix/maturity-review-2026-11-05-b
:docs/improvement-manual
:fix/maturity-review-2026-11-05
:fix/session-subject-required
:fix/ui-design-audit-2026-11-01
:fix/maturity-review-2026-09-25
:lane/D
:lane/B
:fix/src-review-round3
:refactor/domain-scalable
:develop
:feature-frontend-optional-adapter-recipes
:feature-frontend-supply-chain-verification
:feature-frontend-test-registry-evidence-hardening
:frontend-test-registry-evidence-hardening
:feature-frontend-diagnostics-telemetry-runtime
:feature-frontend-i18n-message-formatting-contract
:feature-frontend-design-system-platform
:feature-frontend-form-page-platform
:feature-frontend-reference-feature-vertical-slice
:feature-frontend-routing-release-recovery-runtime
:feature-frontend-http-query-contract-execution
:feature-frontend-application-boundary-runtime
:feature-frontend-typescript-tooling-foundation
:feature-frontend-platform-capability-review
:feature-frontend-performance-route-contract
:feature-frontend-starter-experience-quality-contract
:feature-frontend-responsive-theme-contract
:feature-frontend-ui-primitives-gallery-contract
:feature-frontend-app-shell-navigation-contract
:feature-frontend-runtime-composition-contract
:feature-frontend-ci-quality-gates-contract
:feature-web-vitals-performance-budget-contract
:feature-frontend-release-cache-rollback-contract
:feature-accessibility-baseline-contract
:feature-frontend-project-bootstrap-toolchain-contract
:feature-frontend-operational-runbook-contract
:feature-frontend-contract-compatibility-governance
:feature-frontend-contract-registry-governance
:feature-frontend-browser-security-boundary-contract
:feature-frontend-build-bundle-supply-chain-contract
:feature-tailwind-design-token-styling-contract
:feature-sample-feature-slice-contract-fixture
:feature-frontend-render-recovery-boundary-contract
:feature-routing-navigation-guard-contract
:feature-boundary-mapper-viewmodel-contract
:feature-async-ui-state-contract
:feature-frontend-observability-logging-trace-contract
:feature-frontend-storage-registry-contract
:feature-server-state-caching-contract
:feature-frontend-auth-session-integration-contract
:feature-frontend-error-classification-boundary-contract
:feature-runtime-schema-validation-contract
:feature-api-client-response-envelope-contract
:feature-frontend-env-runtime-config-contract
:feature-frontend-architecture-enforcement-lint-contract
:feature-frontend-test-taxonomy-contract
:feature-frontend-clean-architecture-layering-contract
No Reviewers
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
donghyeon.kang (동현 강)
Clear assignees
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: donghyeon.kang/clean-architecture-frontend-template#25
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
무엇을, 왜
isRefusedOnEveryAttempt(재전송 거절이 결과 불명을 푸는지)가failure.code를 읽는데, 그 값은 기능의mapProblem이 정한다(1112/01-06). 그래서 둘이 틀린다.VALIDATION_FAILED를 자기 code로 바꾸면, 모든 시도가 받는 거절인데도 결과 불명이 풀리지 않는다.VALIDATION_FAILED로 바꾸면, 첫 요청이 반영됐을 수 있는데도 결과 불명이 풀린다.고른 방법과 버린 대안
AppFailure에backendCode를 더한다(선택 칸, 추가만).ENVELOPE_V1operation의 PROBLEM에서 백엔드error.code를 그대로 싣는다. 판정은 이 칸과 status만 읽는다.위험과 영향
createFailure로 실패를 직접 만들어 재전송 거절을 흉내 내던 시험은backendCode를 함께 줘야 결과 불명이 풀린다. 템플릿 안에서는 코디네이터 시험 넷이고 고쳤다. 다운스트림 시험이 같은 방식이면 같은 칸을 더한다(round9 마지막 CHANGELOG [계약]에 적는다).mapProblem이 예외를 던져MAPPING_CONTRACT_VIOLATION이 된 실패에는 싣지 않는다(결과 불명에 남는다).src/contracts/errors.ts는 F3(fix/r9-abort-telemetry)도 고친다. 고친 줄은 겹치지 않는다.검증
desktop, CI env,
scripts/verify.sh(flock).5250ff95에 새 시험만):backend-envelope.test.ts·feature-http-binding.test.ts새 시험 다섯 중 넷 실패(4 failed, 63 passed). Envelope 없는 operation 시험은 고치기 전에도 통과하는 대조군이다. 로그/tmp/claude-gates/r9f2d-red/.application-mutation-admission·form-foundation138 passed. 로그/tmp/claude-gates/r9f2d-green/.e42dbfb7= head 트리): FE-GATE-002·003·005·006·007·010 모두 rc=0. 로그/tmp/claude-gates/r9f2d-gates/.리뷰어가 볼 곳
src/contracts/errors.ts의isRefusedOnEveryAttempt.src/adapters/http/feature-http-binding.ts의 PROBLEM 분기와envelopeCode.관련
docs/reviews/2026-11-round9-01-react.md01-06(PR #23), 이월 1106/03-01(D10 보완)#40으로 병합됐다(main
ee47480c). 이 PR의 head8c1bab29가 #40 브랜치에 merge 커밋으로 들어 있고, #40의 runner merge job 셋이 그 합친 트리로 초록이었다. runner 대기를 줄이려고 이번만 쓴 방식이다(소유자 승인, 2026-11-13).Pull request closed