Feat/issue 935 mm project role - #943
Merged
Merged
Conversation
harminius
force-pushed
the
feat/issue-935-mm-project-role
branch
from
September 17, 2026 10:31
38a257a to
badef90
Compare
MarcelGeo
approved these changes
Sep 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resolves #935
Depends on MerginMaps/python-api-client#323
Adds
@mm_project_role, a project-scoped QGIS variable holding the current user's role on the active Mergin Maps project.The value comes from the project's own metadata, so it resolves offline and costs nothing to read.
mm_project_*variables, and re-read afterproject_status()(so it follows a role change even when there is nothing to sync), after a completed sync, and when a project is opened or created.create_manager()covers the project QGIS restores at startup, which is read beforeinitGuihas built a client to ask with. Prefersproject_info_v2, which carries the role without the file list, and falls back to v1Any failure leaves the stored role alone so an offline start behaves as before.