-
Notifications
You must be signed in to change notification settings - Fork 624
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
Local VRT + Eliminate CSS warnings from build process #8968
base: main
Are you sure you want to change the base?
Conversation
⚡ Deployed with Pantheon Decoupled This build was successfully deployed with Pantheon. You can track the build logs here. 👀 Preview: https://pr-8968-documentation.appa.pantheon.site |
⚡ Deployed with Pantheon Decoupled This build was successfully deployed with Pantheon. You can track the build logs here. 👀 Preview: https://pr-8968-documentation.appa.pantheon.site |
@mel-miller This PR is not at all urgent. Just some clean up that should get your review. |
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.
Works for me.
Thanks @mel-miller! I'm assigning to @rachelwhitton for final review and merge. |
I just resolved the merge conflicts with |
⚡ Deployed with Pantheon Decoupled This build was successfully deployed with Pantheon. You can track the build logs here. 👀 Preview: https://pr-8968-documentation.appa.pantheon.site |
Vulnerable Libraries (1)
More info on how to fix Vulnerable Libraries in JavaScript. 👉 Go to the dashboard for detailed results. 📥 Happy? Share your feedback with us. |
⚡ Deployed with Pantheon Decoupled This build was successfully deployed with Pantheon. You can track the build logs here. 👀 Preview: https://pr-8968-documentation.appa.pantheon.site |
⚡ Deployed with Pantheon Decoupled This build was successfully deployed with Pantheon. You can track the build logs here. 👀 Preview: https://pr-8968-documentation.appa.pantheon.site |
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.
@stevector I added local VRT here in this PR, can you take a look? On another branch I got 8 scenarios passed (screenshot of that has been added to the description at the top of this PR), but on this branch the test result is showing me 4 passed and 4 failed
The TOC stopped working across various templates, for example:
- https://pr-8968-documentation.appa.pantheon.site/guides/mariadb-mysql/kill-mysql-queries
- https://pr-8968-documentation.appa.pantheon.site/certification/study-guide
- https://pr-8968-documentation.appa.pantheon.site/drupal-cron
Headers are smaller in the preview environment compared to production
backstop.json
Outdated
"onBeforeScript": "puppet/onBefore.js", | ||
"onReadyScript": "puppet/onReady.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.
These 2 lines were copied in from an example config file, I think we can remove?
CREATING NEW REFERENCE FILE
WARNING: script not found: /Users/rachelwhitton/documentation/backstop_data/engine_scripts/puppet/onBefore.js
Browser Console Log 0: JSHandle:BackstopTools have been installed.
Browser Console Log 0: JSHandle:BackstopTools have been installed.
Browser Console Log 0: JSHandle:BackstopTools have been installed.
Browser Console Log 0: JSHandle:BackstopTools have been installed.
Browser Console Log 0: JSHandle:BackstopTools have been installed.
Browser Console Log 0: JSHandle:BackstopTools have been installed.
Browser Console Log 0: JSHandle:BackstopTools have been installed.
Browser Console Log 0: JSHandle:BackstopTools have been installed.
WARNING: script not found: /Users/rachelwhitton/documentation/backstop_data/engine_scripts/puppet/onReady.js
@rachelwhitton I'm reassigning to myself to investigate that |
@rachelwhitton I figure out why the Table of Contents stopped working. In the PR that created Release Notes (#8802) I created the documentation/src/templates/changelogs.js Line 23 in 87ec5f5
That Anyway, I don't think we need the |
I'll keep this PR assigned to myself to continue poking at VRT, at least until our 1:1 tomorrow. |
🙃 No, it's used elsewhere so I'll keep the component, just remove this particular usage. |
⚡ Deployed with Pantheon Decoupled This build was successfully deployed with Pantheon. You can track the build logs here. 👀 Preview: https://pr-8968-documentation.appa.pantheon.site |
⚡ Deployed with Pantheon Decoupled This build was successfully deployed with Pantheon. You can track the build logs here. 👀 Preview: https://pr-8968-documentation.appa.pantheon.site |
⚡ Deployed with Pantheon Decoupled This build was successfully deployed with Pantheon. You can track the build logs here. 👀 Preview: https://pr-8968-documentation.appa.pantheon.site |
⚡ Deployed with Pantheon Decoupled This build was successfully deployed with Pantheon. You can track the build logs here. 👀 Preview: https://pr-8968-documentation.appa.pantheon.site |
The volume of warnings within our build process related to CSS order is problematic. Here's an example:
In the latest build of the main branch there are 16 instances of
Conflicting order. Following module has been added:
It is not clear to me how serious these warnings are in and of themselves, but I think the are worth eliminating purely to get rid of the noise that makes it much harder to troubleshoot other warnings and errors with the build process when they occur.
In researching this pattern of warnings I found that the path to resolution seemed to be in ensuring that components/css files were imported in the same order across pages (and potentially imported in the order of usage within a component).
In any case, the build of this PR contains no CSS warnings. The changes in the PR fall into three categories
import
statements within component files to create consistency across components.import
statements. As I was cleaning up these files I was relying on VSCode's hightlighting to point out unusedimport
statements. Some of the removed imports might have been irrelevant to the css ordering errors, but it seemed wise to remove unused imports anyway.Adding BackstopJS Configuration
backstop_data
directory path added to .gitignoreExample result: