MerginMaps / MerginMaps/mobile
time on update of feature is not tracked correctly
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 388
- Forks
- 87
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 20
Description
Project: tc05_default_values; there are 2 bugs in this project, also (https://github.com/MerginMaps/input/issues/2352)
- add a feature and fill in the field "text"
- field "datetime_on_update" is being updated accordingly
- there is the time when you stop typing in the "text" field
- if you save the feature and open it again, you will notice, that the time in "datetime_on_update" is different than the one you save it with
- if you now don't change anything, the time will not change, but if you change the text and save and reopen the feature, the time will be different again
Found on:
iOS 15.7 and Android 11
correct behavior https://app.qase.io/run/INPUT/dashboard/34/a4a83ba5d5ff17755b520b8b3884560c1e07a2a6
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
Reproduce the issue with the tc05_default_values project on iOS or Android using the listed steps. Compare the saved datetime_on_update value with the expected behavior in the Qase run and attached video; the issue does not name an implementation file or test, so trace the feature-edit and save flow first. Done means the timestamp remains correct after reopening and resaving changed text.
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
- 25/100