Remove unused example schemas #2902
Merged
Conversation
This file contains 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
Example schemas are high cost to manually maintain and are prone to diverging from the real schema. We should remove as many as we can that are not used.
GDSNewt
approved these changes
Oct 3, 2024
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.
Example schemas are high cost to manually maintain and are prone to diverging from the real schema. We should remove as many as we can that are not used. This PR aims to remove as many example schemas as we can related to Specialist Documents and Specialist Finders.
Requires following PR merges to pass:
alphagov/finder-frontend#3486
alphagov/government-frontend#3352
alphagov/govuk_schemas#125
https://trello.com/c/7fzxocSX/2813-remove-specialist-document-examples-from-publishing-api
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.