Project lead tools: Optimize district homerooms, improve layout on permissions pages#2545
Merged
kevinrobinson merged 4 commits intomasterfrom Aug 22, 2019
Merged
Conversation
Contributor
Author
|
selfie |
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
1 participant
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.
Who is this PR for?
district project leads
What does this PR do?
District homeroom pages load slowly for some, this optimizes it and supports falling back if short school names aren't provided.
It also updates the layout of the permissions pages to be a bit clearer, and removes some older metrics on sign ins from permissions. These were only ever used internally on the team for debugging issues, and have been replaced by better internal tools. These project lead features are about permissions, not monitoring.
Screenshot (if adding a client-side feature)
adjust permissions
permissions overview
project lead links order
Checklists
Which features or pages does this PR touch?
Does this PR use tests to help verify we can deploy these changes quickly and confidently?