MerginMaps / MerginMaps/mobile
Better error reporting on 400 errors
Open
Nobody has claimed this yet.
enhancement
sync
ui/ux
- Dominant language
- C++
- Stars
- 388
- Forks
- 87
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 20
Description
400 errors often mask issues with geodiff. Mergin returns an error message along with a 400 error. I suggest that we always allow the user (even if needing to click on a *more details* button) to see the detail of this error to aid in our debugging.
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 file, test, or entry point is named. Start by tracing how the mobile app handles HTTP 400 responses from Mergin and geodiff, then inspect the existing error-display flow. Done means the returned error detail is available to users, including through a more-details interaction if needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- api, mobile-dev
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100