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

misc: update web.dev URLs #15534

Merged
merged 8 commits into from
Oct 16, 2023
Merged

Conversation

tunetheweb
Copy link
Member

Summary

Web.dev moved infrastructure this week and the URL formats have changed.

  • Most pages were moved into /article folders
  • trailing slashes were removed
  • anchor id were changes from using dashes to underscores

In most cases there's a redirect in place (though not for the third one sadly), but let's update the URLs to avoid this redirect.

This also updates some URLs that redirect to developer.chrome.com or dequeuniversity.com to go there directly.

Avoid redirects and fix anchor ids.

Related Issues/PRs

@tunetheweb tunetheweb changed the title Update web.dev URLs misc:update web.dev URLs Oct 12, 2023
Copy link
Member

@adamraine adamraine left a comment

Choose a reason for hiding this comment

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

Thanks for going through this Barry!

changelog-pre10.md Outdated Show resolved Hide resolved
changelog-pre10.md Outdated Show resolved Hide resolved
report/test-assets/lhr-6.0.0.json Outdated Show resolved Hide resolved
report/test-assets/lhr-8.5.0.json Outdated Show resolved Hide resolved
@@ -639,7 +639,7 @@
"message": "Utilitza formats de vídeo per al contingut animat"
},
"core/audits/byte-efficiency/legacy-javascript.js | description": {
"message": "Els polyfills i les transformacions permeten als navegadors heretats fer servir funcions de JavaScript noves. No obstant això, molts no són necessaris per als navegadors moderns. Per al teu JavaScript empaquetat, adopta una estratègia de desenvolupament de scripts moderna utilitzant la detecció de la funció mòdul / no mòdul per reduir la quantitat de codi enviat als navegadors moderns, mantenint al mateix temps la compatibilitat amb els navegadors heretats. [Informació sobre com pots utilitzar el JavaScript modern](https://web.dev/publish-modern-javascript/)"
"message": "Els polyfills i les transformacions permeten als navegadors heretats fer servir funcions de JavaScript noves. No obstant això, molts no són necessaris per als navegadors moderns. Per al teu JavaScript empaquetat, adopta una estratègia de desenvolupament de scripts moderna utilitzant la detecció de la funció mòdul / no mòdul per reduir la quantitat de codi enviat als navegadors moderns, mantenint al mateix temps la compatibilitat amb els navegadors heretats. [Informació sobre com pots utilitzar el JavaScript modern](https://web.dev/articles/publish-modern-javascript)"
Copy link
Member

Choose a reason for hiding this comment

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

i18n string changes need to go through the translator pipeline, but I imagine this would be the result anyway. Did you run yarn update:sample-json?

Copy link
Member Author

Choose a reason for hiding this comment

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

No I didn't. When I do that it reverts my changes. Am I missing a step I need to do first? I tried yarn build-all first but no diff.

Copy link
Member

@adamraine adamraine Oct 12, 2023

Choose a reason for hiding this comment

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

I think reverting your changes makes sense. Most of these files (with the exception of en-US & en-XL) we get from the translator engine in g3. So we don't want to edit these files directly.

After this PR lands we can upload the new i18n strings to g3. Then once the new strings go through the translator pipeline we will pull them in before the next release.

Copy link
Member Author

Choose a reason for hiding this comment

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

So revert everything in locales directory but leave all the .js changes?

Copy link
Member Author

Choose a reason for hiding this comment

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

OK did what @brendankenny suggested:

FWIW you'll probably make your life a lot easier backing out the shared/localization/locales/* and sample-flow-result.json/sample_v2.json changes, run yarn update:sample-json, then let the localization pipeline take care of the rest

And that worked this time. Only the en-US and en-XL ones changed.

treemap/app/debug.json Outdated Show resolved Hide resolved
@adamraine adamraine changed the title misc:update web.dev URLs misc: update web.dev URLs Oct 12, 2023
Copy link
Member

@brendankenny brendankenny left a comment

Choose a reason for hiding this comment

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

FWIW you'll probably make your life a lot easier backing out the shared/localization/locales/* and sample-flow-result.json/sample_v2.json changes, run yarn update:sample-json, then let the localization pipeline take care of the rest

core/audits/no-unload-listeners.js Show resolved Hide resolved
@tunetheweb
Copy link
Member Author

Looking more promising now @adamraine and @brendankenny - all tests now passing.

@adamraine adamraine merged commit 19dc786 into GoogleChrome:main Oct 16, 2023
26 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants