Optimization and fixes - #36
Open
edgeinfinity1 wants to merge 6 commits into
Open
edgeinfinity1 wants to merge 6 commits into
edgeinfinity1 wants to merge 6 commits into
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
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.
The userBadges model is bound to users and discussions originally, which means they'll be loaded together with users in call scenarios, making it a very large burden when there's a lot of users and badges.
I made this patch to only bind actively displaying badges to discussions and list users, the complete list will be lazy loaded. This accelerated my deployment 300~1000%, it's a very nessary tweak.
Minor: added slug support for badges page.