Setlist visibility #132
Merged
Setlist visibility #132
Conversation
This file contains 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
Signed-off-by: Andreas Müller <mail@devmount.de>
Signed-off-by: Andreas Müller <mail@devmount.de>
Signed-off-by: Andreas Müller <mail@devmount.de>
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.
Description of the Change
This change introduces two visibility states for setlists: public (default) and private. A green lock indicates that a setlist is private.
When creating or editing a setlist:
When previewing a setlist:
In the list of setlists:
On the dashboard:
Benefits
Gives users the option to create setlists that are only visible to them (e.g. for private events). Also tidies up the list of setlists.
Applicable Issues
Closes #124