MerginMaps / MerginMaps/qgis-plugin
Editor: user unfriendly behaviour when there are only project changes
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 44
- Forks
- 20
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 5
Description
The project changes are filtered from the synchronization when the user has Editor permission. When there are only project changes in the project, and the user hits sync, the plugin tries to synchronize. On the end, there is a "Mergin Maps project tme1/Dkrjtjng synchronized successfully" message, and in the web app, no new version of the project was created.
All of this is correct. Still, the user would see ongoing synchronization which ends in a successful message with no new version on the emerging. I believe this can be misleading. I would prefer to show the project is "Up to date" information with info that, project changes are not considered.
Also, the yellow bar on the top of the "Project status" windows disappears in case of project changes. I am not sure this is intentional.
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 issue #592 in the QGIS plugin with a project containing only project changes and an Editor-permission user, then inspect the synchronization flow and Project status window. Done means the UI reports the project is up to date, explains that project changes are not considered, and confirms whether the yellow status bar should remain visible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100