Open
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
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.
Hey guys!,
So after forking, cloning the repo, I was stuck for 2 days trying to figure out why on earth is the development mode locally taking so long to render views, either initially or at some soon point whilst navigating. After immense researching I found that the fix is by changing config.assets.degug to false. I also found out that using false increases the request time which lead me to do a before and after tail:
before:
after:
I know the difference isn't humongous but I think it would be worth our while and time saving for people who wish to develop if we didn't alter but just included the comments suggested into this file.