Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE ember-improved-instrumentation] Rebase + Tests #13017

Closed
wants to merge 6 commits into from

Conversation

chadhietala
Copy link
Contributor

Rebase and Adds Test For #12550. However this just introduces action instrumentation. There are still issues around instrumenting the router. I have saved off the diff for the time being. https://gist.github.com/chadhietala/2b3065f3da3d8ae6e2ff

Godhuda and others added 4 commits February 26, 2016 10:10
This commit adds instrumentation for interaction events handled by
components. The `before` hook of the instrumentation runs right before
the component’s event handler is invoked, and the `after` hook runs
right after it is invoked.
This commit instruments closure actions.
This instruments the start and end of top-level routing transitions. It
does not run for redirects or intermediate transitions.

There are two events: `router.transition.url` (payload contains the URL)
and `router.transition.named` (payload contains the route name).

The current implementation does not properly handle top-level
transitions that never complete at all; this requires a fix to
router.js.
@krisselden
Copy link
Contributor

Tests seem broken

@chadhietala
Copy link
Contributor Author

Yea, there is some weird stuff around route transitions where certain events are fired in some cases and not others.

@chadhietala chadhietala force-pushed the instrument branch 2 times, most recently from 1f0bc7d to 2ba1336 Compare February 28, 2016 23:55
@chadhietala
Copy link
Contributor Author

@chancancode You ok merging this for the time being and then come back to router instrumentation? Can squash if everything else looks good.

@homu
Copy link
Contributor

homu commented Mar 19, 2016

☔ The latest upstream changes (presumably #13100) made this pull request unmergeable. Please resolve the merge conflicts.

@rwjblue
Copy link
Member

rwjblue commented Apr 10, 2016

@chadhietala - We will definitely need to fix the failing tests before merging (I haven't looked into what exactly is wrong yet).

@rwjblue
Copy link
Member

rwjblue commented Apr 10, 2016

Also, does this need to live on or is it replaced by #13279?

@mixonic
Copy link
Member

mixonic commented Apr 10, 2016

Yeah the comments left on #13279 would also apply to this PR.

@rwjblue rwjblue closed this Aug 18, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants