Admin acccess levels#10680
Merged
Merged
Conversation
Member
Author
|
is not perfeect with showing on the client e.g the next round drop-down is still visible but I can't really think of a good way of handling it without making a bespoke Thing and another good point with next round drop-down |
Member
Author
|
|
MaxIsJoe
approved these changes
Feb 7, 2025
corp-0
reviewed
Feb 7, 2025
|
|
||
| public TAGType TAGType; | ||
|
|
||
| public List<TAGType> NeedsAny; |
Member
There was a problem hiding this comment.
instead of two lists, you could do what we do in clearance code. It is basically the same logic
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.
Changelog:
CL: [New] new system for handling admins ranks and permissions