-
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
Offline mode: Post conflict resolution overlay #20607
Conversation
Generated by 🚫 Danger |
📲 You can test the changes from this Pull Request in WordPress by scanning the QR code below to install the corresponding build.
|
📲 You can test the changes from this Pull Request in Jetpack by scanning the QR code below to install the corresponding build.
|
…nary action click
WordPress/src/main/java/org/wordpress/android/ui/posts/PostResolutionOverlayFragment.kt
Outdated
Show resolved
Hide resolved
WordPress/src/main/java/org/wordpress/android/ui/posts/PostResolutionOverlayListener.kt
Outdated
Show resolved
Hide resolved
WordPress/src/main/java/org/wordpress/android/ui/posts/PostListDialogHelper.kt
Outdated
Show resolved
Hide resolved
…change. Set isStarted and make post a property
Hey @zwarm ! Awesome work! I reviewed the code and tested the app. I found the following:
|
Quality Gate passedIssues Measures |
@zwarm I've pushed a fix for the major issue mentioned earlier. The problem was that we weren't checking whether the PostListMainViewModel had already been started. Consequently, during a configuration change, multiple instances of the PostListEventListener object were being created. These instances were triggering multiple events to the PostConflictResolver object, resulting in multiple toasts being displayed to the user. I have tested the changes and they have resolved the issue, so I am approving the 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.
Great work! LGTM!
@pantstamp - this was a great find. I recall other reports of multiple toasts showing. Thanks for the fix. 🙇 |
Thanks for the video, I wonder if we should disallow swipe to close on landscape? Probably not, but we can try it. |
Hey I think its a good idea to use the Whats New format (also similar to Bloganuary) which it looks like you've done. I've just tidied up the type styles and stuff more appropriate for this case. I didn't have a modal and x button to hand but what you have there is fine. Figma link eYeHXEMDbnFptE40xUqZ2T-fi-2551%3A6479 |
Suspect IssuesThis pull request was deployed and Sentry observed the following issues:
Did you find this useful? React with a 👍 or 👎 |
@osullivanchris - Thank you for the feedback, but somehow I missed the GH ping 🤦 . I'll add a new ticket to make this adjustments in an upcoming version. |
Fixes #20164
This PR updates the dialogs for post version conflicts and autosave available. Instead of the small android dialog, they are now a full page overlay.
CC @osullivanchris - Any design suggestions or comments? Are we completely off base? Went off the iOS screens.
Before
After
Prepare for testing
sync_publishing
flag and restart the appTest Overlay (Run twice - once for Version Conflict & once for Autosave Available)
Regression Notes
Potential unintended areas of impact
The post conflicts are not resolved properly
What I did to test those areas of impact (or what existing automated tests I relied on)
Added
PostResolutionOverlayViewModelTest
andPostResolutionOverlayAnalyticsTrackerTest
What automated tests I added (or what prevented me from doing so)
Relied on existing instrumentation tests
PR Submission Checklist:
RELEASE-NOTES.txt
if necessary.Testing Checklist (strike-out the not-applying and unnecessary ones):