Typescript definitions incorrect
See original GitHub issueWhen using fuse with an options
object that specifies only keys, the type definition suggests the return type ought to be the same as the type of the elements in the searched array. However, this is not the case - the return type is a wrapper object with an item
property (containing the item) and a refIndex
property (which is a number).
Setting includeScore
to true results in a correct type definition.
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
How to overwrite incorrect TypeScript type definition installed ...
Say that I want to use dotenv module in my TypeScript project and install its .d.ts using npm install @types/dotenv --save . Then...
Read more >Vue Typescript definitions incorrect · Issue #3905 - GitHub
It seems going from 1.8.56 to 1.9.6, the constructor for VueSurveyModel has changed, and it no longer accepts parameters.
Read more >Incorrect typescript definition for Azure DevOps Services ...
If I make a call to `https://vsrm.dev.azure.com/jet-tfs/Kepler/_apis/release/definitions/317?api-version=5.0&$top=200` I can see that it's there but the ...
Read more >TypeScript - CustomStore - Incorrect typing definition for the ...
In our solution we created a custom store, that is reused by different components. We found the issue as we added tests for...
Read more >Incorrect type resolution from typings in a case of multiple type ...
It looks like type is incorrectly being resolved from typings definition in a case if there is multiple type definitions are available for...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Updating to 5.0.9 fixed the issue. Thanks!
Sorry, meant >= v5.0.9-beta