MerginMaps / MerginMaps/mobile
Incrementing with default value does not work right
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 388
- Forks
- 87
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 20
Description
What happens
Combining default value and incrementing does behave unexpectedly.
How to reproduce
download project tc05_expression_tickets and open it
record a point
default value of the incrementing field is 11.
When you put lower value than 11, the next feature will have again 11 as default value.
When you enter higher value, the next feature will be incremented by 1.
Screenshots / screencast
https://t24429115.p.clickup-attachments.com/t24429115/fbc457b5-a34a-4167-a0cd-2025b17e973a/increment.mp4?open=true
---
Author of the original task:
Herman Snevajs
Original tags:
migrate to github
Original task URL: https://app.clickup.com/t/862kfp6a1
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
Download the tc05_expression_tickets project, open it in the mobile app, and reproduce the incrementing-field behavior described in the issue. Verify cases where the entered value is below or above the default of 11; done means subsequent features increment correctly rather than resetting to 11.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100