refactor(types): Minor Type Improvements for the ThirdParty
Recipe
#946
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.
Summary of changes
This PR is intended to improve the DX for anyone using
supertokens-node/recipe/thirdparty
. ItTypeProvider
methodsredirectURIQueryParams
field of theTypeProvider.exchangeAuthCodeForOAuthTokens
methodRelated issues
N/A. (Can create a separate issue if desired.)
Test Plan
This is just a simple TypeScript types change. So as long as the project builds, everything should be fine.
Documentation changes
N/A
Checklist for important updates
I was uncertain about whether or not I should update
package.json
(and friends).coreDriverInterfaceSupported.json
file has been updated (if needed)lib/ts/version.ts
frontendDriverInterfaceSupported.json
file has been updated (if needed)package.json
package-lock.json
lib/ts/version.ts
npm run build-pretty
If new thirdparty provider is added,recipe/thirdparty/providers/configUtils.ts
file,createProvider
function.git tag
) in the formatvX.Y.Z
, and then find the latest branch (git branch --all
) whoseX.Y
is greater than the latest released tag.If have added a new web framework, update theadd-ts-no-check.js
file to include thatIf added a new recipe / api interface, then make sure that the implementation of it uses NON arrow functions only (likesomeFunc: function () {..}
).If added a new recipe, then make sure to expose it inside the recipe folder present in the root of this repo. We also need to expose its types.If added a new entry point, then make sure that it is importable by adding it to theexports
inpackage.json