Fixed issue where SPA view names were case-sensitive #1027
Merged
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.
Description
Considering we still have both internal and external customers running into SPA view case sensitivity issues, we need to fix this in Web SDK, so that for both Target and AJO, SPA view names are consistently lowercase across VEC, at.js and Web SDK.
Note: We're fixing this by setting the view name to lowercase both when using the
viewName
supplied underxdm.web.webPageDetails.viewName
, as well as by lowercasing the view decision scopes (these are currently being lowercased at authoring time for TNT/AJO activities created in VEC UI, however in case any views were defined directly via TNT APIs these could still be case-sensitive)Related Issue
https://jira.corp.adobe.com/browse/TNT-48367
Motivation and Context
Screenshots (if appropriate):
Types of changes
Checklist: