fix: convert hash index sample data to object in query wizard#57
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
CahidArda
approved these changes
Jun 19, 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
2 participants
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.
The AI Query Builder sends a few sample documents from the index to the LLM as context. For hash indexes,
hgetallreturns a raw flat array (["title", "My doc"]) instead of an object, because the client runs withautomaticDeserialization: false— which caused the wizard to fail withInvalid request data.This converts the flat array into a
{ field: value }object before sending, so hash indexes work and the LLM gets cleaner data. JSON and string indexes were unaffected since they come back as strings.