MobileNativeFoundation / MobileNativeFoundation/Store
[Feature Request] Enable Configuration of Conflict Resolution Strategies
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Kotlin
- Stars
- 3.4k
- Forks
- 217
- Avg merge
- 18m
- Merged PRs (30d)
- 4
Description
Many use cases will not want to pull immediately after failing to push local changes. We should enable configuration of conflict resolution strategies, such as logging, retrying, canceling.
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
No files, tests, or entry points are identified in the issue. Start by locating the flow that handles failed pushes and pulls, then determine how conflict resolution is currently selected. Done means callers can configure strategies such as logging, retrying, or canceling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100