MerginMaps / MerginMaps/mobile
Inconsistency when evaluating expression between the mobile app and QGIS
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 388
- Forks
- 87
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 20
Description
Description
Some expressions work in QGIS but not in Mergin Maps. For example:
Boolean =1 works in QGIS but in MM Boolean is True works.
Environment
Production
Application (+ app version, build, operating system)
All versions, all platforms
Steps to reproduce
In QGIS, when you have a field which is Boolean, create a drag and drop form. Create a subgroup which its visibility depends on the boolean value. If you type the expression Boolean =1 it works in QGIS but not in MM.
Actual results
Expected results
Screenshots
Preferably add images as HTML element as shown below:
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
The report does not name a file, test, or entry point. Reproduce the Boolean visibility expression in QGIS and Mergin Maps using a drag-and-drop form, then trace how each app evaluates the expression. Done means equivalent Boolean expressions behave consistently on the reported platforms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100