-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[Feature] Reader Improvements #19267
Merged
Merged
Conversation
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
…provements-feature-flag [Reader Improvements] Implement Reader Improvements feature flag
…iner in reader site header new design
Thank you for taking the time, @tiagomar 👍 |
…on-manage-topics-sites-screen [Reader Improvements] Fix follow buton size on "Manage Topics & Sites" screen
Generated by 🚫 dangerJS |
…st-card-minor-tweaks [Reader Improvements] Post card minor tweaks
This new field keeps track if the current status change is final or not, meaning that it was committed and succeeded in the backend or was just an initial status change due to the action being STARTED.
Observe the `followStatusUpdate` LiveData to instantly change the state of the follow button for the recommended blogs card in the Discover feed. It also sets the button as enabled or disabled based on the status updated. Currently there's a small issue that makes the button be enabled even before the final change in state for `followStatusUpdate` because the Discover feed is also updated by another data source (`readerDiscoverDataProvider.discoverFeed`) which is directly hooked to the `ReaderPostTableActionEnded` that is emitted by the Event Bus when there are changes in the underlying table. This issue is fairly small since the worst thing that can happen is the ripple animation showing up but there are other safeguard in place to avoid making duplicate request so the overall state does not get insconsistent.
Use the new `isChangeFinal` field to properly update the enabled/disabled status of the follow button in the Post Detail header.
…w-unfollow-button-responsiveness [Reader Improvements] Fix follow unfollow button responsiveness
…provements-enable-ff [Reader Improvements] Enable ReaderImprovementsFeatureConfig by default
…notes-reader-improvements [Reader Improvements] Update 23.5 RELEASE-NOTES
ravishanker
added
Do Not Merge
In PRs with this label, our automation will fail a require check, preventing accidental merging
and removed
Do Not Merge
In PRs with this label, our automation will fail a require check, preventing accidental merging
labels
Oct 15, 2023
jostnes
approved these changes
Oct 16, 2023
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 ran ReaderTests
locally and looks good, the previously failing test e2eBookmarkPost
now works without issue. The changes look good too. Thanks for fixing the failing test!
ravishanker
removed
the
Do Not Merge
In PRs with this label, our automation will fail a require check, preventing accidental merging
label
Oct 16, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Feature branch of Reader Improvements (ref: pcdRpT-3Eb-p2)