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

Remove specialist topic code from Publishing API #2669

Closed
Closed
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 0 additions & 5 deletions lib/schema_generator/expanded_links.rb
Original file line number Diff line number Diff line change
Expand Up @@ -35,11 +35,6 @@ class ExpandedLinks
# to by the `pages_related_to_step_nav` link type
"related_to_step_navs" => "frontend_links_with_base_path",

# Taxons that have been created by merging old 'legacy' taxons will have
# a reverse link to determine where the replacement Topic Taxonomy taxon
# now resides
"topic_taxonomy_taxons" => "frontend_links_with_base_path",
Copy link
Contributor

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.


# Step by steps that a content items may be a part of but is not essential
# to completing it.
"secondary_to_step_navs" => "frontend_links_with_base_path",
Expand Down