-
Notifications
You must be signed in to change notification settings - Fork 10
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
Usagov 1789 wizard datalayer #2046
Conversation
… of the first slot to match current order of keys.
I am having a hard time testing with the recommended command of I have checked things manually though, and it all mostley looks good to me. The only thing I see that may be awry, is that we are no longer prefixing "t_" before the "Page ID" column for taxonomy terms, though, with the way this has been refactored, this may no longer be necessary? I say lets merge this in, and if we really need to add the "t_" prefix back in, then I can do that as a part of I am seeing a comment from Amy saying "right now we want to hold off so Scott and Gene can test their branch on the dev site" - I'll ping the team and ask if we are ok to proceed forward. |
@DaleMHFrey the html tidy config file is linked here now: https://github.com/usagov/usagov-2021/wiki/tome |
Jira Task
https://cm-jira.usa.gov/browse/USAGOV-1789
Description
Moves the datalayer for wizards out of twig template and builds it with the datalayer event listener.
Fixes 3 issues against current dev, as of 10/29. The last item is being fixed in another ticket:
Taxonomy_Text_1
to"Página principal"
,Taxonomy_URL_1
to"/es/"
instead of"/es"
,
inTaxonomy_URL_6
that have it.Type of Changes
Testing Instructions
Change Requirements
Validation Steps
find . -name '*.html' -type f -print -exec tidy -config ../tidy-config.txt --warn-proprietary-attributes false -mq '{}' \;
diff -brwd --strip-trailing-cr --exclude=_data -I " rel=\"stylesheet\">" -I "<script src=" -I js-view-dom-id --exclude=themes html-dev/ html/ > html.diff
Security Review
Reviewer Reminders
Post PR Approval Instructions
Follow these steps as soon as you merge the new changes.
Review in Test
and add a comment. State whether the change is already visible on cms-dev.usa.gov and beta-dev.usa.gov, or if the deployment is still in process.