-
Notifications
You must be signed in to change notification settings - Fork 174
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
MWPW-160058: Fixes tag matching case logic #3098
Conversation
Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch and validate page speed.
Commits
|
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## stage #3098 +/- ##
==========================================
- Coverage 96.43% 96.34% -0.09%
==========================================
Files 245 245
Lines 55746 56317 +571
==========================================
+ Hits 53757 54258 +501
- Misses 1989 2059 +70 ☔ View full report in Codecov by Sentry. |
This pull request is not passing all required checks. Please see this discussion for information on how to get all checks passing. Inconsistent checks can be manually retried. If a test absolutely can not pass for a good reason, please add a comment with an explanation to the PR. |
@mokimo |
Skipped merging 3098: MWPW-160058: Fixes tag matching case logic due to failing checks |
You could ignore the coverage for thsi line https://github.com/bcoe/c8/blob/main/README.md |
Skipped merging 3098: MWPW-160058: Fixes tag matching case logic due to failing checks |
The problem:
Right now, the milo send-utils.js script compares the tags from adobe.com with the tags in the page.
But before comparing the tags it "lower-cases" ONLY the tags from adobe.com and not the ones from the page:
Proposed solution:
Lower case both set of tag values before comparing them.
Resolves: MWPW-160058
Test URLs:
@mokimo
This is a (fairly large and complex) utilities file that was created long time ago and it does not have any test coverage. We are planing on creating a story to add a full code coverage to all the functionalities in the file, but we should not hold up any small incremental improvements.