-
Notifications
You must be signed in to change notification settings - Fork 5
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
Fix search links #11553
base: all-search-styling
Are you sure you want to change the base?
Fix search links #11553
Conversation
Size Change: +1.1 kB (+0.11%) Total Size: 1.02 MB
ℹ️ View Unchanged
|
doc: { | ||
type: 'Exhibition highlight tour', | ||
uid: '1', | ||
highlightTourType: 'text' as HighlightTourType, |
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.
is this a thing? I think highlightTourType
can only be one of bsl
or audio
because those share the same data. Exhibition text
is its own type I think?
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's for handling the legacy exhibition-guides type
isContentType, | ||
} from './content-types'; | ||
|
||
export type HighlightTourType = 'audio' | 'bsl' | 'text'; |
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.
ah
What does this change?
Work we did on the all search, to make the results links work, broke some other links on the site and had to be reverted
This reimplements those changes, without breaking the other links.
How to test
How can we measure success?
All the site links and search links work
Have we considered potential risks?
The link-resolver.test now covers everything so we should be good, unless I've missed places we are creating links without the linkResolver function