Add Customer Impersonation Token to ENV#17
Merged
bc-alexsaiannyi merged 1 commit intomainfrom Jun 23, 2023
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
BC-krasnoshapka
approved these changes
Jun 19, 2023
yurytut1993
approved these changes
Jun 19, 2023
bc-alexsaiannyi
force-pushed
the
token
branch
2 times, most recently
from
a077805 to
1d0595d
Compare
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
3 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.
What/Why
Previously, we've auto generated a Customer Impersonation Token (CIT) on each GraphQL request within
bigCommerceFetchmethod. Now we change the logic and move this step on the side of User. That means from now on User should generate CIT by himself/herself and put it on.envfile and regenerate once it is going to expire. README is updated with link to our docs how to generate CIT via endpoint.Additionally,
revalidateoption has been removed from fetching so onlycache: force-cacheoption is stayed in place. This removes next warning:Warning: fetch for https://store-xxx.mybigcommerce.com/graphql on ... specified "cache: force-cache" and "revalidate: 900", only one should be specified.