MerginMaps / MerginMaps/mobile
Reuse last value option doesn't work well with default values
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 388
- Forks
- 87
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 20
Description
In the project documentation/form_setup, there is a Surveyor field with default value (@mergin_username).
In this case, 'Reuse last value' option should not be available. But it is and it is misleading, as the user expect, that when he checked it, his value would be reuse in next feature, but it isn't. Default value is used instead.
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
Review project documentation/form_setup and the Surveyor field configuration to trace how default values interact with the “Reuse last value” option. Confirm the expected behavior: the option should not be available when a default value is configured, or should not imply that reuse overrides that default. No test file or implementation entry point is mentioned.
Written by the indexing model from the issue text.
Assessment
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100