integrations(hypequery): import substituteParameters instead of copying it

[ShawnChen-Sirius]

Follow-up cleanup now that both halves have landed:

• Add chdb/hypequery — run hypequery on embedded chDB #63 shipped the chdb/hypequery adapter, which carried a byte-for-byte copy of hypequery's substituteParameters/escapeValue because they weren't exported yet.
• Export substituteParameters and escapeValue for adapter authors hypequery/hypequery#239 exported them, released in @hypequery/clickhouse@2.1.2.

So the copy can go.

Change

• import { substituteParameters } from '@hypequery/clickhouse' and delete the duplicated substituteParameters/escapeValue helpers (~40 lines).
• Bump the @hypequery/clickhouse optional peer to >=2.1.2 (first version with the exports) and the devDependency to ^2.1.2.

Why it's safe

• Anyone using chdb/hypequery is by definition using hypequery, so @hypequery/clickhouse is already installed — the runtime import adds no real dependency, and it stays an optional peer.
• Using hypequery's own substituteParameters guarantees the SQL the adapter renders stays byte-identical to hypequery's built-in HTTP adapter, instead of relying on a copy that can drift.

Verification

• Installed @hypequery/clickhouse@2.1.2 and confirmed both substituteParameters and escapeValue are exported (runtime + .d.ts).
• test/v3/integrations/hypequery.test.ts passes 4/4 against the real imported helper (the run logs show hypequery itself engaged).

🤖 Generated with Claude Code

Note

Replace local substituteParameters implementation with import from @hypequery/clickhouse

Removes the local substituteParameters and escapeValue helpers from hypequery.mjs and delegates parameter substitution to the upstream library instead. Bumps the @hypequery/clickhouse dependency from ^2.1.1 to ^2.1.2 and tightens the peer dependency range to >=2.1.2 to match.

^{Macroscope summarized da149e3.}

[ShawnChen-Sirius]

@chibugai, review it

[Copilot]

Pull request overview

This PR cleans up the chdb/hypequery integration by removing a previously inlined copy of hypequery’s parameter substitution/escaping logic and instead delegating to the upstream @hypequery/clickhouse implementation (now exported as of 2.1.2).

Changes:

• Bump @hypequery/clickhouse devDependency to ^2.1.2 and peer dependency to >=2.1.2.
• Replace the local substituteParameters/escapeValue helpers in integrations/hypequery.mjs with an import of substituteParameters from @hypequery/clickhouse.
• Update the lockfile accordingly.

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated 1 comment.

File	Description
package.json	Updates @hypequery/clickhouse dev + peer dependency versions to require the first release that exports substituteParameters.
package-lock.json	Syncs lockfile with the dependency bump and updated peer dependency metadata.
integrations/hypequery.mjs	Switches from duplicated helper code to using upstream substituteParameters for byte-identical SQL rendering.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[chibugai]

Reviewed — OCR (opus-4-8) deep pass + a manual read of the diff. Small, well-scoped cleanup; LGTM with one judgment call to make consciously.

Clean:

• Local substituteParameters/escapeValue removed with no dangling references; the imported substituteParameters is wired consistently through query(), stream(), and render() (each substitutes once from raw params — no double-substitution).
• Peer bump to >=2.1.2 matches the first version that exports the helpers, so the range is honest.
• Since these helpers were originally copied verbatim from hypequery's core/utils.ts, importing them back is exactly what keeps the rendered SQL byte-identical — and the 4/4 hypequery.test.ts run backs that up.

One thing to weigh (already flagged by Copilot, so not re-posting inline): the new top-level import { substituteParameters } from '@hypequery/clickhouse' turns this previously dependency-light module into one that throws ERR_MODULE_NOT_FOUND at import time if the optional peer is absent — before chdbAdapter() is ever called. Your rationale (anyone importing this adapter already has hypequery installed) holds for normal usage; the edge cases are tooling that eagerly imports every subpath export, or dependency scanners. A lazy/guarded import with a targeted error (per Copilot's suggestion) would preserve the optional-peer contract — non-blocking, your call.

No correctness or safety issues in the diff.