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
While using the FintectureClient class from the SDK, I noticed that most of the functions have generic Promise<object> return types. As TypeScript developers, having specific return types for each function can greatly improve our development experience. This allows us to take full advantage of TypeScript's static type checking and IntelliSense functionality.
Here's a breakdown of the current functions and their return types:
I'd like to propose that the other methods also have specific return types, rather than the generic Promise<object>. This way, developers can have a clearer understanding of the data structure that each function will return, which can help in reducing potential runtime errors and improving development efficiency.
If the exact return type structure is documented or known, it would be great to see them represented in the TypeScript definitions.
Thanks for considering this enhancement!
The text was updated successfully, but these errors were encountered:
Hello, team!
While using the
FintectureClient
class from the SDK, I noticed that most of the functions have genericPromise<object>
return types. As TypeScript developers, having specific return types for each function can greatly improve our development experience. This allows us to take full advantage of TypeScript's static type checking and IntelliSense functionality.Here's a breakdown of the current functions and their return types:
While some methods, like
getPisConnect
andgetAisConnect
, are correctly typed:I'd like to propose that the other methods also have specific return types, rather than the generic
Promise<object>
. This way, developers can have a clearer understanding of the data structure that each function will return, which can help in reducing potential runtime errors and improving development efficiency.If the exact return type structure is documented or known, it would be great to see them represented in the TypeScript definitions.
Thanks for considering this enhancement!
The text was updated successfully, but these errors were encountered: