MerginMaps / MerginMaps/mobile
Value must be a number constraint error in autogenerated fid field
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 388
- Forks
- 87
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 20
Description
When I create feature or add to table with no geometry and have fid field in form with autogenerated value visible as "Autogenerate" in form input I get "Value must be a number" constraint error and can't save form. When I delete fid field from form I can save new feature as usual. Before 1.0.2 update it worked.
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 reported form submission with a feature or table that has no geometry and an autogenerated fid field displayed as "Autogenerate." Compare this behavior with the pre-1.0.2 behavior and trace the form validation path. Done means the form saves successfully without deleting the fid field and no longer reports "Value must be a number."
Written by the indexing model from the issue text.
Assessment
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100