feat: methods for getting and refreshing long-lived tokens #2
Conversation
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
tonypeng
requested changes
Apr 15, 2025
Collaborator
tonypeng
left a comment
tonypeng
left a comment
There was a problem hiding this comment.
Thanks for adding these in! Some small requests in the comments
|
|
||
| export const GetLongLivedTokenResponseSchema = z.object({ | ||
| access_token: z.string(), | ||
| "token_type": z.string(), |
| redirect_uri: redirectUri, | ||
| code, | ||
| }, ExchangeAuthorizationCodeResponseSchema); | ||
| return response as ExchangeAuthorizationCodeResponse; |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I've implemented methods for getting and refreshing long-lived tokens for Threads users, allowing the app to stay authenticated without requiring reauthentication every hour.
Additionally, I refactored the authorization code exchange method to use the internal
_apiPostmethod, ensuring consistency across the codebase.I’ve manually tested these changes, and everything works as expected with no impact on other parts of the codebase.