Add TypeScript typings#31
Add TypeScript typings#31resynth1943 wants to merge 9 commits intodevelopit:masterfrom resynth1943:master
Conversation
|
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please visit https://cla.developers.google.com/ to sign. Once you've signed (or fixed any issues), please reply here with What to do if you already signed the CLAIndividual signers
Corporate signers
ℹ️ Googlers: Go here for more info. |
|
@googlebot I signed it! |
|
CLAs look good, thanks! ℹ️ Googlers: Go here for more info. |
|
/cc @developit |
|
@resynth1943 - these look good! I'm wondering if it would be possible to somehow re-export Axios's original typings though? That would mean folks could move between the two libraries without causing any type errors. I'm not super knowledgeable about TypeScript, so I might be suggesting something that is totally impossible 😂 |
Co-authored-by: Jason Miller <developit@users.noreply.github.com>
Co-authored-by: Jason Miller <developit@users.noreply.github.com>
Hmm, not sure... I'll try and look into it. |
Co-authored-by: Ryan Christian <33403762+RyanChristian4427@users.noreply.github.com>
|
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
|
Oh my god, not this again. |
|
@googlebot I fixed it. |
|
CLAs look good, thanks! ℹ️ Googlers: Go here for more info. |
|
Hiya @resynth1943! This looks pretty nice, and it's clear there's more type safety possible by moving the types into a dedicated declaration file like you have done here. Any ideas for how we could combine this with the JSDoc tweaks from #33?I was thinking maybe we could have the declaration be where all the interfaces are kept, and then use JSDoc to associate those in the library code (mainly as a development aide). Too weird? |
|
Oh dang, I've never had to maintain JSDoc |
|
could somebody by any chance add TS types to this repo or create a |
|
Oh shit this is still open? |
|
possible to merge this? would be greatly appreciated! also, could somebody please add TS types to this repo or create a @types/redaxios? thank you |
|
@samwhiteiv Types are already shipped, and have been for quite a while. They're just generated from JSDoc rather than authored directly. See #33 |
|
noted. thanks @rschristian |
|
If types have already been shipped for this, should we close this PR? |
|
Yep, sorry about that. There might still be some improvements to be had in the JSDoc types though. |
|
Well, it seems there is no update on this issue, so bad. I can't get
|
bad?
That's correct behavior for now, as neither type exists. Mind creating a new issue for adding these types? Comments in a closed PR aren't great for tracking potential hiccups for users. |
Hey there! I don't use this library, but I noticed people were asking for TypeScript typings: #22, so I thought I would help out and add them. If there's anything you're not happy with, hit me up :-)