fix(types): fixing hits and results types in connectHits and connectInfiniteHits #4820
+12
−2
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.
connectHits
The types
Hit
andAlgoliaHit
are mostly the same.https://github.com/algolia/instantsearch.js/blob/21b6c53d4b1a3f3dd3a2375a5cfe0a31bef6ded6/src/types/results.ts#L60-L63
As of today, the hits exposed via results indeed contain __position and __queryID.
connectInfiniteHits
While trying use
InfiniteHitsRenderState
in Angular InstantSearch I noticed howhits
andresults
while being part of the state expored byconnectInfiniteHits
are not actually visible on the type.