-
Notifications
You must be signed in to change notification settings - Fork 16
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
Add govspeak support for finder summary #3145
base: main
Are you sure you want to change the base?
Conversation
@kashifatcha is this still being worked on? Do you mind if we mark it as a draft for now (to stop alerts in our team channel)? |
@yndajas I have marked it as a draft PR for now |
1f533fe
to
c057fca
Compare
Introduce new schema structures for finder summaries. Specialist finder summaries are now converted to GovSpeak. In order to send GovSpeak the schema structure will have to match multiple content type definitions, but other finders such as licence finder will still be sending a string summary. We need to support both.
e8c2822
to
d60e101
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.
LGTM 👍 one non-blocking comment below
@@ -288,6 +288,9 @@ | |||
{ | |||
type: "null", | |||
}, | |||
{ | |||
"$ref": "#/definitions/multiple_content_types", |
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'd suggest moving this into its own commit, and then doing the 'regenerate schemas' bit in a second commit. Makes it easier to see what you've changed vs the auto-generated changes that come later.
What
The schemas in Specialist Publisher have a summary property which can (and often does) contain HTML. This is exposed to the publisher on the “edit metadata” form (example).
The property should be stored in the schema as GovSpeak, and rendered in the publisher <textarea> as GovSpeak, but presented downstream as HTML.
Why
Publishers shouldn’t be expected to have to write HTML. And if they do use GovSpeak, the developer has to manually convert this to HTML before it can be processed.
https://trello.com/c/FHjlxPUv/3410-add-govspeak-support-for-summary-property-in-specialist-publisher-schemas
This application is owned by the publishing platform team. Please let us know in #govuk-publishing-platform when you raise any PRs.
Follow these steps if you are doing a Rails upgrade.