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
{{ message }}
This repository has been archived by the owner on Jan 10, 2023. It is now read-only.
I'm working with checkAndRenewSession(profile: UserProfile, authToken: string): Promise<AuthResponse> right now, which the parent component thinks returns any. I understand this is compiled to JS before the parent component integrates it, removing the typescript annotations. I never noticed any complaints about a lack of a .d.ts file like with other components. Can we create and pass one to maintain types between projects?
I have been thinking about creating a type declaration file (index.d.ts) for some time and have done some research on how to do it, so I'd like to take on this one as soon as I wrap up my current work on CSS integration, which should happen in the next few days.
Awesome, thanks! I have to admit, I have tried creating .d.ts files for a few libraries that didn't have typescript support and I have failed a bunch. I don't know why it's so hard, but it seems like a really useful skill to have if we're working in typescript long term.
Do you know why it doesn't complain about the lack of typing like it does with a normal untyped library?
I'm working with
checkAndRenewSession(profile: UserProfile, authToken: string): Promise<AuthResponse>
right now, which the parent component thinks returnsany
. I understand this is compiled to JS before the parent component integrates it, removing the typescript annotations. I never noticed any complaints about a lack of a.d.ts
file like with other components. Can we create and pass one to maintain types between projects?@cdoremus
The text was updated successfully, but these errors were encountered: