-
Notifications
You must be signed in to change notification settings - Fork 142
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
feat(storefront): strf-9174 Product object in quick view on localhost not consistent with prod: #991
feat(storefront): strf-9174 Product object in quick view on localhost not consistent with prod: #991
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -457,7 +457,9 @@ internals.buildReqHeaders = ({ | |
'stencil-custom-templates': templates, | ||
}; | ||
|
||
if (!request.headers['stencil-config'] && stencilConfig) { | ||
const config = request.headers['stencil-config']; | ||
|
||
if ((!config || config === '{}') && stencilConfig) { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. So the header can be undefined and can be empty object? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Not sure about undefined, I decided not to touch existing check just not to break anything. However, it definitely could be empty object. I saw that during debugging. |
||
headers['stencil-config'] = JSON.stringify(stencilConfig); | ||
} | ||
// eslint-disable-next-line no-param-reassign | ||
|
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.
this is duplicate of line 30 above