This repository has been archived by the owner on Oct 2, 2019. It is now read-only.
silence logging of requests for assets in development #683
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
not really that useful now since the asset logging is muted
|
love it. much better solution. |
pkarman
added a commit
that referenced
this pull request
Oct 8, 2015
silence logging of requests for assets in development
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Asset logging, e.g.
is basically just noise, so added a gem that silences it. Also removed the now-not-really-useful
ASSETS_DEBUGconfig flag, which was apparently added to reduce the number of asset logging messages received. Now it's a non-issue, and it makes JS debugging easier since they appear in separate files.