fix: add missing Experience Cloud targets #4578
Merged
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
This PR adds missing Experience Cloud targets to the js-meta XML validation.
CristiCanizales
added
the
type:community-contrib
|
This issue has been linked to a new work item: W-12188466 |
randi274
approved these changes
Dec 8, 2022
|
Thanks for contributing @muenzpraeger !😁 |
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.
What does this PR do?
This PR adds missing Experience Cloud targets to the js-meta XML validation.
What issues does this PR fix or reference?
@W-12188466@
Functionality Before
The js-meta validation is missing two Experience Cloud targets for LWR sites.
Functionality After
The js-meta validation no longer declares the valid targets as invalid.