-
Notifications
You must be signed in to change notification settings - Fork 17
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
Update Govspeak usage #1884
Update Govspeak usage #1884
Conversation
da2b2b9
to
f26ae87
Compare
f26ae87
to
06864eb
Compare
30839ed
to
1b82283
Compare
1ffd246
to
b05ae00
Compare
424b4af
to
6f0db61
Compare
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.
I've been relatively thorough going through examples of pages rendered by these templates to avoid another rollback like we had on manuals. It all seems good to me, with the proviso that I don't know how to check the /service_sign_in/ paths.
Edit to add: Have now also confirmed the sign in routes look fine.
I believe this is good to go.
The legacy attachment partial needed the `sanitize` method to be used with an allow list of attributes and tags.
6f0db61
to
ff5b3f6
Compare
What
This updates the way Govspeak wraps content.
Templates updated:
Why
The previous method of adding content to Govspeak - using the
content
attribute - is being deprecated in favour of usingdo
blocks with sanitized markup. See alphagov/govuk_publishing_components#1632 for more details.Visual changes
None.
Merged changes are automatically deployed to staging and production.
Make sure you follow the guidance for deployments before you merge.
Check your branch is being deployed in the Release app, after merging.