MerginMaps / MerginMaps/mobile
Reuse value stress test
Open
Nobody has claimed this yet.
bug
forms
- Dominant language
- C++
- Stars
- 388
- Forks
- 87
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 20
Description
When recording the feature with lots of fields and all of them are checked for reuse value for next record, the feature breaks.
Steps to reproduce:
- download input-testing/forms_widgets project
- record the feature
- fill all the fields and set reuse value on every field
- save the feature
- record next feature
- you can see that any value is filled in any field
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 downloading the mentioned input-testing/forms_widgets project and reproducing the failure through the feature-recording flow. Trace how reuse values are stored after saving a feature and applied when recording the next one; done means each field receives its own previously selected value when all fields have reuse enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100