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
The TypeScript definitions for lmdb appear to be missing the getAsync method, which exists in the JavaScript version. This results in TypeScript users not being able to use getAsync with proper type safety or autocompletion support.
Property 'getAsync' does not exist on type 'Database'.
Expected Behavior:
The getAsync method should be defined in the TypeScript type definitions so that it can be used without errors in TypeScript projects.
Current Workaround:
Currently, I'm working around this issue by casting the database object or using a //@ts-ignore comment, but this is not ideal for maintaining type safety.
Environment:
lmdb version: [latest]
TypeScript version: [latest]
Suggested Fix:
Add getAsync to the TypeScript definitions of lmdb to match the JavaScript API.
Thank you for maintaining this project! I look forward to the resolution of this issue.
The text was updated successfully, but these errors were encountered:
Description:
The TypeScript definitions for
lmdb
appear to be missing thegetAsync
method, which exists in the JavaScript version. This results in TypeScript users not being able to usegetAsync
with proper type safety or autocompletion support.Steps to Reproduce:
Install the latest version of
lmdb
:Use the
getAsync
method in a TypeScript file:The TypeScript compiler throws an error:
Expected Behavior:
The
getAsync
method should be defined in the TypeScript type definitions so that it can be used without errors in TypeScript projects.Current Workaround:
Currently, I'm working around this issue by casting the database object or using a
//@ts-ignore
comment, but this is not ideal for maintaining type safety.Environment:
lmdb
version: [latest]Suggested Fix:
Add
getAsync
to the TypeScript definitions oflmdb
to match the JavaScript API.Thank you for maintaining this project! I look forward to the resolution of this issue.
The text was updated successfully, but these errors were encountered: