fix: route canonical HWPX values through record rules - #74
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
변경 내용
/api/v1/documents/generate에서TEMPLATE_RULES기반 canonical key HWPX 생성을 지원합니다.application_options경로는 유지합니다.원인
Renewal의 canonical key가
/documents/generate에서 dynamic-label 방식으로 해석되어 HWPX 필드 검색에 실패했습니다.검증
성/명label 요청 성공150 passed672 passed, 5 skippedgit diff --check통과전체 suite의 Qdrant 통합 테스트 4건은
qdrant-client미설치로 실패했으며, 이번 범위에서는 수정하지 않았습니다.