MerginMaps / MerginMaps/mobile
Constraint to a single field affects all the form
Open
Nobody has claimed this yet.
bug
forms
relations
- Dominant language
- C++
- Stars
- 388
- Forks
- 87
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 20
Description
If I have a constraint on a field it appears to affect the whole form.
I will send an example with more details to reproduce.
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
The issue names no files, tests, or reproducible example; begin by obtaining the promised example and reproducing the field-constraint behavior in the mobile form. Then locate the form-validation entry point and compare field-level and form-level scope. Done means a constraint on one field no longer affects unrelated fields, with a regression test if the project has one.
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
- Needs clarification
- Newbie friendliness
- 15/100