-
Notifications
You must be signed in to change notification settings - Fork 339
Fix display of local announcement banner #1822
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
Conversation
if (is_remote) { | ||
document.write(`<aside class="bd-header-announcement d-print-none" aria-label="{{ banner_label }}"></aside>`); | ||
fetch("{{ theme_announcement }}") | ||
.then(res => {return res.text();}) | ||
.then(data => { | ||
if (data.length === 0) { | ||
console.log("[PST]: Empty announcement at: {{ theme_announcement }}"); | ||
return; | ||
} |
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.
If I'm reading this correctly, the aside
tag will get written first, even if data.length === 0
. Seems like we wouldn't want that to happen?
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.
oh good point, let me fix it
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.
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.
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.
By the way, PR 1808 has a test case that checks that the banner gets rendered when theme announcement is local.
As an aside, one reason I was holding off on 1808 was that I wanted to see if someone had any thoughts about how to write the tests I added in a more efficient way, but that could always be done in a follow-up PR.
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.
Oh - sorry about that, I should have checked. I'll pause here and let you finish 1808 first, thanks!
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.
No worries, I think it's awesome you jumped in to help fix the problem :)
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.
@melissawm, I edited some updates you made to the docs about the theme announcement, so if you could double check that my rewrite is accurate that would be awesome
Closing in favor of #1808, thanks all. |
Closes #1817
A small refactor of the announcement banner display logic to fix the display of local announcement banners.