MerginMaps / MerginMaps/mobile
"0.0" not accepted on first try for a float (postgresql) field
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 388
- Forks
- 87
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 20
Description
**Description**
I have a postgis layer with a float field that is set up in QGIS with a range widget as
In MM app entering the value "0.0" is not accepted as valid on a first try.
To workaround the problem the user can write first "0.1" then correct back to "0.0" which is now accepted.
**Application (+ app version, build, operating system)**
2026.2.0
**Steps to reproduce**
See above
**Actual results**
**Expected results**
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 issue in the Mergin Maps mobile app using the reported QGIS/PostGIS layer, a float field, and its range widget. Trace the field-value validation path and compare entering 0.0 directly with entering 0.1 first; done means 0.0 is accepted on the first attempt.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql
- Domain
- databases, mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100