You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using TypeScript > 5.1, there are numerous type check errors, most of which are related to Element implicitly has an 'any' type because expression of type 'string' can't be used to index type (…), but also Parameter (…) implicitly has an 'any' type.. My tsconfig.json already includes "skipLibCheck": true so there is not a lot I can do to work around besides pinning the TS version.
Steps to reproduce
Include typesense in a JS project and e.g. import type { SearchResponse } from "typesense/lib/Typesense/Documents";. Run tsc >= 5.2.
Expected Behavior
The project compiles without any issues.
Actual Behavior
There are a lot of typescript issues, probably depending on how much typesense interfaces are imported.
Metadata
Typesense Version:
1.7.2
OS:
MacOS 14.1.1
Node 21.2.0
The text was updated successfully, but these errors were encountered:
Yeah, just started using this, and it's unusable in typescript because of the errors. At least for me, Trying to figure out how I can ignore typechecks on this library only.
Description
When using TypeScript > 5.1, there are numerous type check errors, most of which are related to
Element implicitly has an 'any' type because expression of type 'string' can't be used to index type (…)
, but alsoParameter (…) implicitly has an 'any' type.
. My tsconfig.json already includes"skipLibCheck": true
so there is not a lot I can do to work around besides pinning the TS version.Steps to reproduce
Include typesense in a JS project and e.g.
import type { SearchResponse } from "typesense/lib/Typesense/Documents";
. Runtsc
>= 5.2.Expected Behavior
The project compiles without any issues.
Actual Behavior
There are a lot of typescript issues, probably depending on how much typesense interfaces are imported.
Metadata
Typesense Version:
1.7.2
OS:
MacOS 14.1.1
Node 21.2.0
The text was updated successfully, but these errors were encountered: