Skip to content

fix: use upstream Polyglot parser - #709

Merged
kvlonge merged 2 commits into
mainfrom
feat/use-upstream-polyglot
Sep 17, 2026
Merged

kvlonge merged 2 commits into
mainfrom
feat/use-upstream-polyglot

Conversation

@kvlonge

@kvlonge kvlonge commented Sep 17, 2026

Copy link
Copy Markdown
Contributor

Why

SQLBuild still depended on a temporary Polyglot fork even though active upstream releases are available. Upstream 0.11.0 also retains one Snowflake parser gap for a dynamic bracket expression applied after a VARIANT path.

Changes

  • replace polyglot-sql-chio 0.9.3 with upstream polyglot-sql 0.11.0
  • keep parser and SQL-test cache identities tied to the installed upstream distribution
  • normalize unsupported Snowflake variant:path[dynamic_expression] analysis input to the equivalent GET(variant:path, dynamic_expression) form without changing authored or executable SQL
  • cover comments, quoted strings, nested brackets, validation, and the real compile CLI path

Verification

  • uv sync --all-extras
  • focused unit and CLI integration tests
  • make check-ci
  • public repository hygiene scan

@kvlonge
kvlonge enabled auto-merge (squash) September 17, 2026 21:16
@kvlonge
kvlonge merged commit 5fc1178 into main Sep 17, 2026
18 checks passed
@kvlonge
kvlonge deleted the feat/use-upstream-polyglot branch September 17, 2026 21:54
Sign up for free to 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