Skip to content
This repository has been archived by the owner on Dec 23, 2017. It is now read-only.

Feature/perf bar #242

Merged
merged 1 commit into from
Jun 11, 2015
Merged

Feature/perf bar #242

merged 1 commit into from
Jun 11, 2015

Conversation

msecret
Copy link
Contributor

@msecret msecret commented Jun 4, 2015

No description provided.

@@ -14,5 +14,8 @@ <h1 id="hero-heading" class="text--display">Explore Campaign Finance Data</h1>
</div>
</form>
</div>
<script type="application/javascript">
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be wrapped in {% if debug %}...{% endif %}?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I actually want these performance marks to be present all the time. I can explain more in a meeting, but essentially these are custom metrics that we could track for various pages. If we keep these marks, it means that performance tracking tools like new relic, or google analytics will automatically pick them up.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, that's cool. Didn't know window.performance.mark was a thing!

@jmcarp jmcarp merged commit 1a15055 into fecgov:develop Jun 11, 2015
@jmcarp jmcarp removed the plz-review label Jun 11, 2015
@jmcarp
Copy link
Contributor

jmcarp commented Jun 11, 2015

@msecret do we have to do anything to get the extra performance metrics into New Relic?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants