feat(next): add getAccessToken and getOrganizationToken for pages router #782
Conversation
This file contains 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
wangsijie
force-pushed
the
wangsijie-log-9712-getaccesstoken-for-nextjs-pages-router
branch
from
845025e
to
ddec4ea
Compare
charIeszhao
approved these changes
Aug 12, 2024
wangsijie
deleted the
wangsijie-log-9712-getaccesstoken-for-nextjs-pages-router
branch
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.
Summary
add getAccessToken and getOrganizationToken methods for pages router
Users can now use
getAccessToken(request, response, 'resource-indicator')to get access token directly in your pages router. AndgetOrganizationTokenis also available to get organization token.This PR also updates the sample project, and remove some content to keep it simple.
Testing
Unit tests and local tested.
Checklist
.changeset