Closed rismehta closed 4 months ago
Performance | Accessibility | Best-Practices | SEO | |
---|---|---|---|---|
Scores | 92 | 96 | 96 | 75 |
Performance | Accessibility | Best-Practices | SEO | |
---|---|---|---|---|
Scores | 100 | 96 | 96 | 75 |
Id | Impact |
---|---|
label-title-only | serious |
target-size | serious |
Id | Impact |
---|---|
label-title-only | serious |
target-size | serious |
Id | Impact |
---|---|
label-title-only | serious |
target-size | serious |
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 81.73%. Comparing base (
41e4b47
) to head (d49fcce
).
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
pls avoid referencing internal jira issues in public.
pls avoid referencing internal jira issues in public.
Referring to internal JIRA IDs in GitHub repositories is a practice we have consistently followed. However, we avoid including internal Adobe VPN links in commit messages. Including JIRA ID's can enhance traceability and make it easier to track issues and changes over time.
This practice is also implemented in other Adobe GitHub projects, such as in this example: https://github.com/adobe/aem-core-wcm-components/pull/2804 https://github.com/adobe/aem-core-wcm-components/releases/tag/core.wcm.components.reactor-2.25.0
In some instances, if a GitHub issue is logged, so you won't find a corresponding JIRA ticket.
@review @vdua DOD(Yes)
Description
Related Issue
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: