-
Notifications
You must be signed in to change notification settings - Fork 685
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PWA-3154:GraphQL cacheable requests always have Authorization Bearer … #4240
Conversation
|
__esModule: true, | ||
default: jest.fn(() => 'auth') | ||
})); | ||
// jest.mock('@magento/peregrine/lib/Apollo/links/authLink', () => ({ |
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.
Please donot comment line like these .. remove it from code
@@ -1,6 +1,6 @@ | |||
import { createHttpLink } from '@apollo/client'; | |||
|
|||
import createAuthLink from '@magento/peregrine/lib/Apollo/links/authLink'; | |||
// import createAuthLink from '@magento/peregrine/lib/Apollo/links/authLink'; |
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.
remove code
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.
Done
How will signed in customer functionality work with the authLink removed?
|
deploy pr-test |
deploy pwa-pr-test |
#4240) * PWA-3154:GraphQL cacheable requests always have Authorization Bearer header * PWA-3154:Removing Commented lines * Update index.spec.js.snap * Update index.spec.js.snap --------- Co-authored-by: Aanchal Pawar <97873570+glo82145@users.noreply.github.com>
Description
GraphQL cacheable requests always have "Authorization Bearer" header
Steps to test the behaviour :
1- sign up.in Venia.magento.com or any PWA store
2- login
3- check network tab on any page and search for GraphQL requests which should be cached such as CMSPages
4- check the request header you will not find Authorization Bearer header exist
5- Varnish will cache that request's response.
Related Issue
Closes # https://jira.corp.adobe.com/browse/PWA-3154
Acceptance
Verification Stakeholders
Specification
Verification Steps
Test scenario(s) for direct fix/feature
Test scenario(s) for any existing impacted features/areas
Test scenario(s) for any Magento Backend Supported Configurations
Is Browser/Device testing needed?
Any ad-hoc/edge case scenarios that need to be considered?
Screenshots / Screen Captures (if appropriate)
Breaking Changes (if any)
Checklist