-
Notifications
You must be signed in to change notification settings - Fork 334
feat: allow extra arguments in Insights API #1210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -6,6 +6,9 @@ export type AutocompleteInsightsApi = ReturnType< | |
typeof createSearchInsightsApi | ||
>; | ||
|
||
export type WithArbitraryParams<TParams extends Record<string, unknown>> = | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It's technically an all-purpose utility type, but since it's only being used here for now, it seemed like an unnecessary hassle to move it to |
||
Record<string, unknown> & TParams; | ||
|
||
export type InsightsParamsWithItems<TParams extends { objectIDs: string[] }> = | ||
Omit<TParams, 'objectIDs'> & { | ||
items: AlgoliaInsightsHit[]; | ||
|
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The way
mapToInsightsParamsApi
is typed is what's causing the typing issues I was encountering. When I inline the implementation ofmapToInsightsParamsApi
directly, the issue disappears.I'm not sure what's going on exactly in how TypeScript interprets it all, but when unioning a strict record with an arbitrary record, the generic type
TInsightsParamsType
loses all the mandatory properties and the return type only containsobjectIDs
.I'm doubtful we can fix this at the
mapToInsightsParamsApi
level, so the pragmatic option seems to cast.Lmk if you have a working option that works better.