-
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
Remove specialist topic code from Publishing API #2669
Closed
unoduetre
wants to merge
19
commits into
main
from
2417-remove-specialist-topic-code-from-publishing-api-l
Closed
Changes from 1 commit
Commits
Show all changes
19 commits
Select commit
Hold shift + click to select a range
bf0fa5f
Remove topic taxonomy taxons
unoduetre b155257
Remove topic taxonomy taxons (dist)
unoduetre 234c0ee
Remove links to topics
unoduetre 00f784c
Remove links to topics (dist)
unoduetre a624df0
Remove topic content schema
unoduetre 2f69bb1
Remove topic content schema (dist)
unoduetre ad572f9
Remove topics from email alert types
unoduetre 2a8893b
Remove topics from email alert types (dist)
unoduetre ddaf127
Remove topic tags
unoduetre 513f78f
Remove topic tags (dist)
unoduetre e20c58c
Fix specs other than Pact specs
unoduetre ac09a5a
Revert removing topic taxonomy taxons
unoduetre 09d159a
Revert removing topic taxonomy taxons (dist)
unoduetre f7ba0ff
Fix Pact specs
unoduetre 1ec47ae
Remove specialist topics from database
unoduetre aab4de5
Merge branch 'main' into 2417-remove-specialist-topic-code-from-publi…
unoduetre 97884ee
Remove topic from allowed_document_types.yml
unoduetre 524c8ba
Fix after merging main
unoduetre e684811
Remove topic from allowed_document_types.yml (dist)
unoduetre File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
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.
It sounds like
topic_taxonomy_taxons
were to do with mapping specialist topics to taxonomy topics, so I think it's fair to assume that this field is no longer required. It also looks like this attribute isn't being used in the publishing apps or in the frontend apps anyhow 👍So let's cherry pick bf0fa5f and b155257 into a fresh PR. Linking to that grep in the commit message/PR description, so that it's easy to review and merge with confidence that nothing will break.