Repository navigation
feat(query): support bind parameters - #31
Merged
Merged
Conversation
Contributor
Author
|
@leonkenneth could you review this? You requested the |
leonkenneth
approved these changes
Oct 7, 2026
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.
Summary
paramsto the public query request model$name) and positional ($1) JSON scalar bind valuesImpact analysis
queryand its accumulated/raw variants accept bind values through their shared request model.paramsis omitted unless supplied.The live Lakehouse OpenAPI already exposes this optional field. The current v0.13.0 spec tag predates its documentation, so this PR deliberately does not advance the specs submodule until the documentation PR is merged and tagged.
Validation
git diff --check