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

add instructions_to_publishers to schemas #2972

Merged
merged 1 commit into from
Nov 11, 2024

Conversation

Harriethw
Copy link
Contributor

We want to add a field to all Content Blocks that
will be a short string containing an internal-only message.

This adds the field instructions_for_publishers
to a shared default schema file, and then sets it
as optional on content blocks.

Although this is a Content Block specific field,
it did not make sense to include it in the
details object because we are using that schema
for all custom public-facing fields on a block. We have already set precedent for adding Content
Block specific top level fields with
content_id_alias.


⚠️ This repo is Continuously Deployed: make sure you follow the guidance ⚠️

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.

Copy link
Contributor

@pezholio pezholio left a comment

Choose a reason for hiding this comment

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

Yep, I think this is the way to go - LGTM 👍

We want to add a field to all Content Blocks that
will be a short string containing an internal-only
message.

This adds the field `instructions_for_publishers`
to a shared default schema file, and then sets it
as optional on content blocks.

Although this is a Content Block specific field,
it did not make sense to include it in the
`details` object because we are using that schema
for all custom public-facing fields on a block. We
have already set precedent for adding Content
Block specific top level fields with
`content_id_alias`.
@Harriethw Harriethw force-pushed the content-modelling/677-instructions-to-publishers branch from c691f64 to 4b63ff8 Compare November 11, 2024 10:07
@Harriethw Harriethw merged commit 54685a9 into main Nov 11, 2024
40 checks passed
@Harriethw Harriethw deleted the content-modelling/677-instructions-to-publishers branch November 11, 2024 11:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants