Handle new sync v2 errors

Open
#4,791 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
cpp
Domain
mobile

Research direction

Start from the sync v2 error parsing that #4757 added, since this issue builds on it. Work out how a received DataSyncError with its list of offending files can be surfaced to the user with clear guidance to rename or delete those files before syncing again. Done means the user sees the affected files and can resolve them and synchronize successfully. The issue does not name the UI or sync files, so confirm the design with maintainers before starting.

Written by the indexing model from the issue text.

Description

enhancement sync

Sync v2 introduced some new errors, which are currently getting parsed (done in #4757). However we could improve the handling even better by trying to act based on the received error.

Example:

  • received DataSyncError with the list of offending files
    -> we should let user deal with this issue by renaming/deleting... the file, so they can synchronize again
Dominant language
C++
Stars
394
Forks
91
Avg merge
2d 10h
Merged PRs (30d)
16

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MerginMaps/mobile

All issues in MerginMaps/mobile

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.