chore: rename role -> membership#546
Closed
gmaclennan wants to merge 2 commits intomainfrom
Closed
Conversation
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
2 participants
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.
Depends on https://github.com/digidem/mapeo-schema/pull/172 and a new version of @mapeo/schema being published.
Renames "role" to "membership".
New naming convention:
membership: each device in a project has a membership record, that defines their role in the project. The docId of a membership record is the device ID, and the only other property it currently has is the roleId assigned to the device.role: a role record defines a set of capabilities. There are some built-in roles (project owner, blocked user, left project), and roles which in the future will be editable by project members ("coordinator" and "participant").