wordpress-mobile / wordpress-mobile/WordPress-Android
[GB-Integration] Make sure the change detection logic works on gb-mobile
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 3.2k
- Forks
- 1.4k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 69
Description
Expected behavior
A gutenberg post should not be marked with Local changes is the user doesn't make any edit to it.
Actual behavior
The post is marked with Local changes even if you just open and close the new gb-mobile editor.
Steps to reproduce the behavior
- Open a GB post
- Don't make any changes
- Tap back to go to the posts list
- The "modified" version of the post is uploaded in bg.
Tested on https://github.com/wordpress-mobile/WordPress-Android/pull/8522
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the gb-mobile editor flow and the tested context in WordPress-Android PR #8522. Reproduce the issue by opening a Gutenberg post, making no edits, returning to the posts list, and checking whether it is uploaded as modified. Done means an untouched post is not marked with "Local changes" or uploaded as modified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100