Remove declaration_text from forms (part 2/2) - #3108
Merged
Merged
Conversation
lfdebrux
force-pushed
the
ldeb-remove-declaration-text--part-2
branch
from
September 11, 2026 11:54
b69b0f4 to
6792689
Compare
lfdebrux
force-pushed
the
ldeb-remove-declaration-text--part-2
branch
2 times, most recently
from
September 18, 2026 05:51
50e5227 to
d4ef1e5
Compare
lfdebrux
marked this pull request as ready for review
September 21, 2026 09:45
stephencdaly
previously approved these changes
Sep 21, 2026
lfdebrux
dismissed
stephencdaly’s stale review
September 21, 2026 16:10
The merge-base changed after approval.
stephencdaly
previously approved these changes
Sep 21, 2026
lfdebrux
dismissed
stephencdaly’s stale review
September 22, 2026 05:59
The merge-base changed after approval.
Remove the `declaration_text` column from the `forms` and `form_translations` tables.
lfdebrux
enabled auto-merge
September 22, 2026 12:21
stephencdaly
previously approved these changes
Sep 22, 2026
lfdebrux
dismissed
stephencdaly’s stale review
September 22, 2026 12:26
The merge-base changed after approval.
lfdebrux
force-pushed
the
ldeb-remove-declaration-text--part-2
branch
from
September 22, 2026 12:28
d4ef1e5 to
f6ddfc9
Compare
|
🎉 A review copy of this PR has been deployed! You can reach it at: https://pr-3108.admin.review.forms.service.gov.uk/ It may take 5 minutes or so for the application to be fully deployed and working. If it still isn't ready For the sign in details and more information, see the review apps wiki page. |
stephencdaly
approved these changes
Sep 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What problem does this pull request solve?
The
declaration_textattribute on the forms model has been replaced with thedeclaration_markdownattribute and deprecated. It is no longer read in forms-runner or read or updated in forms-admin.Removing the deprecated attribute completely will simplify the form model and reduce the possibility of confusion.
Removing the attribute from the forms model will not remove it from the form document model or change existing form document contents, but will stop if from being present in new form documents.
This change will prevent
declaration_textbeing copied from a form document to a form model when copying a form form or reverting a draft form, but there are no form documents in the production database which have declaration_text but not declaration_markdown that could cause issues 1.This PR tells adds migrations and updates the schema to delete the
declaration_textcolumn(s).This PR should not be merged until #3107 has been merged and deployed to production.
Things to consider when reviewing
Footnotes
This was verified with the following SQL query:
Prior to https://github.com/govuk-forms/forms-runner/pull/2334, the only situation when the
declaration_textattribute was read was whendeclaration_markdownwas blank.There are two forms in the production database where
declaration_markdownis blank anddeclaration_textis present, however, these were reported as bugs by a form creator, as they had wanted to remove the form declaration. ↩