fix(source): emit UTF-8 route columns and skip SQL function names - #26
Merged
Merged
Conversation
함수 이름을 테이블로 오인하지 않고 미해석 근거와 뒤의 실제 관계를 보존한다. 해당 언어의 회귀 검사와 필수 검증으로 계약을 확인했다.
ictechgy
marked this pull request as ready for review
October 1, 2026 02:38
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
1 participant
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.
Server route declarations now count non-ASCII source columns in the contract's UTF-8 bytes. SQL table-valued function operands keep unresolved evidence instead of fabricated table relations.
Validation: both original failures reproduced; focused regressions, all tests, clippy, coverage92.19%, CLI contract and strict rules/symbol-cycle self-analysis.
Review: GLM SQL-family review completed; tested function skipping and preservation of actual table operands. The UTF-8 route-column regression fails before the fix and passes afterward.