MerginMaps / MerginMaps/mobile
Range widget issues after validation refactoring
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 388
- Forks
- 87
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 20
Description
These issues on range widget were found during testing:
-
User can type in more decimal places than allowed in QGIS
-
Input ignores
Allow NULLoption from QGISRangewidget option. (NOTE: this is not NOT NULL constraint)
-
1e+111 is a valid number, 1e+1111 has error "Value must be a number". Probably different error would be better
-
When inserted really big number, +- signs are active but doesn't work
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 at the range widget validation path and compare its behavior with the QGIS Range widget options named in the issue, especially decimal precision and Allow NULL. Reproduce the listed large-number and sign-input cases; done means each reported behavior has appropriate validation and input handling.
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