Skip to content
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

Copy over new version of Milo's geo-based locales #130

Closed
wants to merge 1 commit into from

Conversation

@aem-code-sync
Copy link

aem-code-sync bot commented Jul 13, 2023

Hello, I'm Franklin Bot and I will run some test suites that validate the page speed.
In case there are problems, just click the checkbox below to rerun the respective action.

  • Re-run PSI Checks

@codecov-commenter
Copy link

codecov-commenter commented Jul 13, 2023

Codecov Report

❗ No coverage uploaded for pull request base (main@dd33b71). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #130   +/-   ##
=======================================
  Coverage        ?   96.36%           
=======================================
  Files           ?        6           
  Lines           ?      468           
  Branches        ?        0           
=======================================
  Hits            ?      451           
  Misses          ?       17           
  Partials        ?        0           

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@aem-code-sync
Copy link

aem-code-sync bot commented Jul 13, 2023

Page Scores Audits Google
/?martech=off Lighthouse returned error: ERRORED_DOCUMENT_REQUEST. Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 401) PSI

Copy link
Contributor

@JasonHowellSlavin JasonHowellSlavin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Alphabetizing for the win!

@meganthecoder
Copy link
Contributor

@hparra There's no ui or functionality to verify here, right? It's just adding the new lang and reg properties and alphabetizing?

@hparra
Copy link
Author

hparra commented Jul 14, 2023

@meganthecoder There is new functionality in Milo that is enabled when these values exist. You can confirm in test urls that HTML lang attribute now only uses language subtag instead of full tag, e.g <html lang="en"> vs. <html lang="en-US">. See adobecom/milo#915 and linked issue for more details. Milo features use getConfig().locale and do not read locale from this attribute.

@meganthecoder
Copy link
Contributor

@hparra Cool, I updated the description to reflect that and assigned myself to verify. Is the reg tag being used yet? I didn't see anything in the PRs you mentioned.

@meganthecoder meganthecoder self-assigned this Jul 14, 2023
@hparra
Copy link
Author

hparra commented Jul 14, 2023

Is the reg tag being used yet?

Not yet. A couple of new features use it and I will begin porting existing features to use it one by one -- those changes will be in Milo only but it will affect all Milo consumers. There will be additional comms of those.

@aem-code-sync
Copy link

aem-code-sync bot commented Jul 14, 2023

Page Scores Audits Google
/customer-success-stories?martech=off Lighthouse returned error: ERRORED_DOCUMENT_REQUEST. Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 401) PSI
/la/customer-success-stories?martech=off Lighthouse returned error: ERRORED_DOCUMENT_REQUEST. Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 401) PSI

Copy link
Contributor

@meganthecoder meganthecoder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are a few locales added that we don't support in bacom. Also, when I was testing, I saw that CaaS cards weren't loading for la

cl: { ietf: 'es-CL', lang: 'es', reg: 'CL', tk: 'oln4yqj.css' },
cn: { ietf: 'zh-CN', lang: 'zh', reg: 'CN', tk: 'puu3xkp' },
co: { ietf: 'es-CO', lang: 'es', reg: 'CO', tk: 'oln4yqj.css' },
cr: { ietf: 'es-419', lang: 'es', reg: 'CR', tk: 'oln4yqj.css' },
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

BACOM doesn't support cr (costa rica), and if you notice, we didn't have it in our config before. We redirect this locale to la. Reference: https://wiki.corp.adobe.com/pages/viewpage.action?pageId=2301888547

Suggested change
cr: { ietf: 'es-419', lang: 'es', reg: 'CR', tk: 'oln4yqj.css' },

cz: { ietf: 'cs-CZ', lang: 'cs', reg: 'CZ', tk: 'aaz7dvd.css' },
de: { ietf: 'de-DE', lang: 'de', reg: 'DE', tk: 'vin7zsi.css' },
dk: { ietf: 'da-DK', lang: 'da', reg: 'DK', tk: 'aaz7dvd.css' },
ec: { ietf: 'es-419', lang: 'es', reg: 'EC', tk: 'oln4yqj.css' },
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same for ec (ecuador)

Suggested change
ec: { ietf: 'es-419', lang: 'es', reg: 'EC', tk: 'oln4yqj.css' },

fr: { ietf: 'fr-FR', lang: 'fr', reg: 'FR', tk: 'vrk5vyv.css' },
gr_el: { ietf: 'el', lang: 'el', reg: 'GR', tk: 'fnx0rsr.css' },
gr_en: { ietf: 'en-GR', lang: 'en', reg: 'GR', tk: 'pps7abe.css' },
gt: { ietf: 'es-419', lang: 'es', reg: 'GT', tk: 'oln4yqj.css' },
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same for gt (guatemala)

Suggested change
gt: { ietf: 'es-419', lang: 'es', reg: 'GT', tk: 'oln4yqj.css' },

ph_en: { ietf: 'en', lang: 'en', reg: 'PH', tk: 'pps7abe.css' },
ph_fil: { ietf: 'fil-PH', lang: 'fil', reg: 'PH', tk: 'ict8rmp.css' },
pl: { ietf: 'pl-PL', lang: 'pl', reg: 'PL', tk: 'aaz7dvd.css' },
pr: { ietf: 'es-419', lang: 'es', reg: 'PR', tk: 'oln4yqj.css' },
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same for pr (puerto rico)

Suggested change
pr: { ietf: 'es-419', lang: 'es', reg: 'PR', tk: 'oln4yqj.css' },

@hparra
Copy link
Author

hparra commented Jul 14, 2023

There are a few locales added that we don't support in bacom

This should be OK. locales is just a source of truth for mappings. locales should NOT be used to enable or disable a particular locale. I can remove but it makes syncing more difficult.

Also, when I was testing, I saw that CaaS cards weren't loading for la

This is probably not OK and is the sort of thing I was afraid of. Can we sync on this so I can understand what is happening?

@hparra hparra added the do not merge PR should not be merged yet label Jul 17, 2023
@hparra
Copy link
Author

hparra commented Jul 17, 2023

Waiting for adobecom/milo#945

@JasonHowellSlavin
Copy link
Contributor

@meganthecoder
Copy link
Contributor

I believe a different solution was determined here: adobecom/milo#963

@hparra Can this PR be closed?

@hparra
Copy link
Author

hparra commented Jul 24, 2023

@meganthecoder I was waiting until handoff to close all PRs but I think we're ok.

@hparra hparra closed this Jul 24, 2023
@hparra hparra deleted the hparra-patch-2 branch July 24, 2023 22:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do not merge PR should not be merged yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants