MerginMaps / MerginMaps/qgis-plugin
Validation: warn if user has form unsupported by the mobile app
Open
Nobody has claimed this yet.
enhancement
validation
- Dominant language
- Python
- Stars
- 44
- Forks
- 20
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 5
Description
Some combinations of form setup are not supported by Input and we should try to warn users about that:
- using custom UI file (only auto-generate and drag&drop designer are supported)
- custom python init functions are not supported
- tabs in drag&drop designer are only supported at the top level, and there must not be a mixture of tabs + other widgets
Also some widgets are not supported by Input, which may be also good to note, e.g. classification, color, unique values, json edit, list, key/value, enumeration, binary (blob)
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
No file or test is named. Start by locating the form-validation entry point in the Python QGIS plugin and trace how form setup and widget types are inspected for mobile compatibility. Done means users are warned for each listed unsupported form configuration and widget without warning for supported setups.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- mobile-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100