-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
feat: Add basic router instrumentation for @sentry/ember #2784
Conversation
This will add routing instrumentation for Ember transitions to @sentry/ember. The import will be dynamically loading depending on configuration settings with to not increase bundle size.
279ebcd
to
d80ee32
Compare
size-limit report
|
packages/ember/addon/instance-initializers/sentry-performance.ts
Outdated
Show resolved
Hide resolved
…rformance integration gets bound as otherwise default integrations won't be included
packages/ember/addon/instance-initializers/sentry-performance.ts
Outdated
Show resolved
Hide resolved
…operly. Split off router instrumentation to allow for use in testing
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.
@k-fish thanks for contributing this, it's exciting to have first-class support for route changes in yet another popular framework ❤️
Looked at previous reviews, at least #2784 (comment) needs to be addressed before this is mergeable.
I'm marking this with a "request changes" and added an item to the TODO in the PR description for visibility of where we stand.
@rhcarvalho that comment was actually resolved already, I spread the existing integrations now on the line below, and add this Ember instrumentation as an additional integration. |
JS code-wise looks good, I'm not able to tell much about ember-specific code though. Left one question. Feel free to merge once addressed. |
Summary
This will add routing instrumentation for Ember transitions to @sentry/ember.
beforeModel
model
andafterModel
will come in a later PR.Looking for feedback specifically on using the route names in lieu of urls like React. There isn't as clean of a way to match urls like we do with react-router, so I'm currently using format for Ember's registry
router:<route-name>
.Screenshot
Added tracing route to the dummy so navigating to the new route can be tested.


Todo