[FIX]: Update Highlight type definition to support array fields and optional attributes#134
Open
Nikhiladiga wants to merge 1 commit intotypesense:masterfrom
Open
Conversation
…ptional attributes
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.
Change Summary
HighlightandHighlightExtended: missing snippets and indices fields per API docs #129This PR updates the Highlight and HighlightExtended TypedDict definitions to correctly support the response structure for array fields introduced in Typesense v30.2+.
Previously, the static type definitions strictly assumed highlight fields would only return singular string properties. This caused false-positive static analysis errors (in mypy, pyright, etc.) when developers attempted to access array-based highlight data.
PR Checklist