wordpress-mobile / wordpress-mobile/WordPress-Android
[Jetpack Social] Convert `_wpas_skip` metadata to `_wpas_skip_publicize`
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 3.2k
- Forks
- 1.4k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 69
Description
Currently some of our clients are using _wpas_skip metadata to represent the sharing social accounts that were manually disabled by the user. Back-end is migrating to a new standard, using the key _wpas_skip_publicize. Android never supported the legacy way and from this PR started to support _wpas_skip_publicize, but we might get the legacy _wpas_skip metadata in PostModel that might've been added in another client. The purpose of this issue is to detect if the metadata contains any _wpas_skip and then migrate it to the new standard _wpas_skip_publicize.
Legacy key: _wpas_skip_<keyringConnectionID>
New key: _wpas_skip_publicize_<publicizeConnectionID>
When receiving a post with any legacy keys in the metadata, we should update it with the new format. It's very important to use the correct ID: legacy key used the keyring connection ID and the new key uses the publicize connection ID.
Discussion: p1690306257631299-slack-C05362VSXFU
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 at PostModel metadata handling and trace how keyring connection IDs map to publicize connection IDs. Verify that every wpas_skip entry is migrated to wpas_skip_publicize, while preserving the intended disabled social accounts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100