This repository was archived by the owner on Jun 10, 2019. It is now read-only.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ZacharyKearns Wrapping the inline
<script>
tag in an if-statement prevents the Raven-related console errors, but that's because the if-statement will never be true. So this also prevents theRaven.config
method from ever being called. That's because when this script tag runs, Raven hasn't been loaded because it's loaded asynchronously w/ adefer
attribute on line 37 in thehead
(this was introduced as a performance improvement in PR #932).Removing the
defer
would probably fix this (and there would be no need for the if-statement either, since Raven would have already been loaded synchronously from CDN).@kylemh I see three options here:
defer
from the Raven CDN script for now (simple fix)Thoughts?