-
Notifications
You must be signed in to change notification settings - Fork 177
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-156940 AU price display #3115
Conversation
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## stage #3115 +/- ##
=======================================
Coverage 96.35% 96.35%
=======================================
Files 245 245
Lines 56316 56329 +13
=======================================
+ Hits 54261 54274 +13
Misses 2055 2055 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks much better to me @bozojovicic, just one move proposal comment left! can you create AU drafts so we can see it in action?
@@ -258,6 +258,10 @@ export default async function init(el) { | |||
firstCol.parentElement.classList.add(`row-${parsed.key}`, 'con-block'); | |||
firstCol.remove(); | |||
cols[1].classList.add('row-wrapper'); | |||
if (locale.prefix === '/au') { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can't this logic be in merch.js?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typically in merch's initService, you know you will need merch, and you could eventually check for AU & hero?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@npeltier I removed this whole change related with hero-marquee from this PR. The request is :
- if we have strikethru price next to the ABM then the annual price needs to go to new line
- if there is no strikethru price, then ABM and annual price need to be in the same line
- this counts for hero-marquee component
But it is just too complicated change for something that is asked for AU only. And now I see that we have some marquee component, similar to hero-marquee ... So, let's go without this change. If they don't like it, we can discuss it again. It is not well defined anyway.
Therefore, there will be no au-merch.js
file. Only au-merch.css
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What I mean by "not well defined"? They just sent few example screenshots in figma file. They never wrote in Jira some specific requirements like : do changes A and B in component C on page D.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good to me now, thanks @bozojovicic :)
content: '\A'; | ||
white-space: pre; | ||
} | ||
merch-card [slot='heading-m'] [is="inline-price"] .price-annual-prefix, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
merch-card styles do not belong here. They should go in global.css.js in mas web-components.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@npeltier @yesil we need some decision here. We had this piece of CSS in libs/features/mas/web-components/src/global.css.js before. Nicolas proposed to move all such changes to au-merch.css which will be loaded on AU pages only. Do you think that this part should be an exception and that I should keep it in global.css.js ? Or it is better like this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bozojovicic (cc @yesil ) the two informations are not necessary contradictory.
i say i don't like having AU css (and logic back then) in all of the code,
ilyas says that he does not like having card WC styling in milo styles.
@yesil do you think that styling is generic to all m@s consumers? i would rather keep it in milo for now
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@npeltier part of the CSS rules like the following look generic to me for annual price formatting.
anything that is for annual price formatting should stay in global.css.js IMO.
merch-card [slot='heading-m'] [is="inline-price"] .price-annual-prefix + .price-annual
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@yesil CSS rules that we have now in au-merch.css I initially had in
- libs/blocks/table/table.css
- libs/features/mas/web-components/src/global.css.js
- libs/features/mas/web-components/src/variants/mini-compare-chart.css.js
and then we decided to move all of that to au-merch.css and load that file for AU pages only.
If I move this part to global.css.js, then I need to do the same for the part I copied from mini-compare-chart.css.js
And then only few rules will stay in au-merch.css and then this files loses its purpose.
For me, both approaches do the job. I personally vote to keep it all in au-merch.css. But I just need some decision which part goes where.
CC @npeltier
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Discussed with @npeltier , I'm fine with keeping these styles in Milo au specific file.
@bozojovicic Have added the following comments to the jira as well
The rest of regression looks ok to me. If GWP approves to go as is, we can add verify and Ready for stage labels. |
@afmicka @Roycethan I added couple of fixes.
|
@bozojovicic
cc @afmicka |
This is the cleaner version of PR #3065
ABM price on Australian pages must be displayed together with annual price in brackets. Few examples from Figma :
Test URLs :
https://main--cc--adobecom.hlx.live/au/products/photoshop?milolibs=mwpw156940auabm2--milo--bozojovicic
https://main--cc--adobecom.hlx.live/au/products/illustrator?milolibs=mwpw156940auabm2--milo--bozojovicic
https://main--cc--adobecom.hlx.live/au/products/photoshop/plans?milolibs=mwpw156940auabm2--milo--bozojovicic
https://main--cc--adobecom.hlx.live/au/products/illustrator/plans?milolibs=mwpw156940auabm2--milo--bozojovicic
https://mwpw156940auabm2--milo--bozojovicic.aem.page/au/docs/library/kitchen-sink/merch-card
Resolves: MWPW-156940
Test URLs: