PWA-2971: [bug]: Gallery item Add To Cart configurable product redire… #4001
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
…ct URL doesn't match tile URL - prefix url suffix with slash to fix redirect - update test expectation
anthoula
added
the
version: Patch
|
…ct URL doesn't match tile URL - use resourceUrl util to generate redirect link
jcalcaben
approved these changes
Nov 10, 2022
m2-community-project
bot
added
Progress: approved
and removed
Progress: ready for review
labels
|
run cypress |
|
Successfully started codebuild job for |
LogERROR ON TASK: cypressTests |
|
run lighthouse-desktop |
|
Successfully started codebuild job for |
|
run lighthouse-mobile |
|
Successfully started codebuild job for |
|
QA Approved. |
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
…ct URL doesn't match tile URL
Description
Prefix URL with a
/so it uses the base URL instead of being relativeRelated Issue
Closes #3854.
Acceptance
Verification Stakeholders
@dpatil-magento
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