Draft
Conversation
Contributor
|
Wow, thanks @jamiehaywood |
|
This looks pretty good! |
Contributor
Author
|
@ozamarripa a couple of reasons for picking Jest, but the main ones are:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a first pass at rewriting the whole library in TS.
If you want immediate utility out of this PR, you could cherry pick commit
59e19b0which has 90% of all the type declarations in atypesfolder which mirror the existing JS structure. All you would need to do is add a"types"key to thepackage.jsonfile and point at the types folder.Otherwise, things still
TODO:exchange-code-for-token.js(w/ accompanying.d.tsfileget-auth-urls.js(w/ accompanying.d.tsfiletokens.js(w/ accompanying.d.tsfilePromise<unknown>)package.json