-
Notifications
You must be signed in to change notification settings - Fork 390
Add storefront private token header #962
Add storefront private token header #962
Conversation
|
||
if (this.storefrontAccessToken && privateToken) { | ||
logger(this.storefrontClass().config).warning( | ||
'You have both private and public storefront access tokens. The private token will be used.', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Logging here instead of earlier at validateConfig
because the config params doesn't include the public access token at that point. I could do a blanket log.info at the earlier stage but I feel like that's a little bit spammy
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree - this shouldn't be a super common case but it's nice to nudge folks to fix it!
|
||
if (this.storefrontAccessToken && privateToken) { | ||
logger(this.storefrontClass().config).warning( | ||
'You have both private and public storefront access tokens. The private token will be used.', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree - this shouldn't be a super common case but it's nice to nudge folks to fix it!
Reverts #961
Adding an extra flag to specify the use of the private tokenAdding a warning line to anyone who has both a private and public token
This hopefully avoids any issues that may be caused by the new working private token headers