fix: adapt Hybrid Approach mapping table for new SEO optimized URLs #1392
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
…t and category page URLs * document more specific `apiToken` cookie requrements for Hybrid Approach
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
apiTokencookie requirements for Hybrid ApproachPR Type
[x] Bugfix
What Is the Current Behavior?
The Hybrid Approach Mapping Table had rules for pre PWA 3.0 URLs for products and categories.
What Is the New Behavior?
The Hybrid Approach Mapping Table now works with PWA 3.0 SEO optimized URLs for products and categories.
Does this PR Introduce a Breaking Change?
[x] No
Other Information
AB#84743