MerginMaps / MerginMaps/mobile
inconsistent save/discard behavior
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 388
- Forks
- 87
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 20
Description
When I am in the middle of capturing a feature and decide to abort the operation, I get inconsistent behaviour.
When I am doing geometry capture and try to abort, I am being asked if I want to discard the changes with Yes and No.
When I am editing the form, I am being asked Do I want to save changes with Yes and No.
as someone with short attention span, I try to read the messages once on a platform and assume it is the same for other parts!
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 reproducing the abort flows for geometry capture and form editing, then compare the two confirmation dialogs. The issue is done when both flows use consistent save or discard wording and behavior, with the result checked on the affected mobile app paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- design, mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100