-
Notifications
You must be signed in to change notification settings - Fork 273
WS-2469: Add live pulse to most read page rank. #13909
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
Open
shayneahchoon
wants to merge
8
commits into
latest
Choose a base branch
from
WS-2469
base: latest
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+32
−0
Open
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
92e7295
WS-2469: Add live pulse to most read page rank.
shayneahchoon 2121059
Merge branch 'latest' into WS-2469
shayneahchoon 3b31604
WS-2469: Add live pulse to most read page rank.
shayneahchoon 6a9bbfa
Merge branch 'WS-2469' of github.com:bbc/simorgh into WS-2469
shayneahchoon 1debf4b
Merge branch 'latest' into WS-2469
shayneahchoon da162b1
WS-2469: Add live pulse to most read page rank.
shayneahchoon 9a3c003
Merge branch 'WS-2469' of github.com:bbc/simorgh into WS-2469
shayneahchoon 31ac036
Merge branch 'latest' into WS-2469
shayneahchoon 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 hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
I see there is a back-end PR to add an
isLiveprop to the response. Will that be used here instead?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.
Heya, I'm going to can the PR you've mentioned. I drafted it upon waiting for a reply from product. Neil is happy for our current changes to go forward as is without needing to check the expiry date.
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.
+1 on this. At the moment the logic suggests that if a live page was no longer being updated (hence, no longer live), the label and icon will still show.
I imagine we don't need this calculated down to a tee (e.g. with polling to check if an article is still live), but it seems like the other PR checks the start/end times of an article being live so that seems preferable.