-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
feat(replay): Add note about potential Angular performance impact #6267
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
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Not sure why link isn't working |
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.
Hmm, not sure if we actually need this, given that we've only received two reports so far?
But I might be missing something/not be up to date, so feel free to merge it if y'all discussed this already.
Co-authored-by: Lukas Stracke <[email protected]>
@Lms24 We talked about this briefly in a meeting, this was a potential solution in order to be extra cautious. It's hard for us to determine actual impact since we're relying on 2 layers of feedback. |
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.
Fair enough, thanks for explaining
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.
@billyvg Can we only show this on the Session Replay instructions for Angular - https://docs.sentry.io/platforms/javascript/guides/angular/session-replay/
Right now, it shows up on every single instruction for each platform (Ember, Gatsby, etc.) which I think is unnecessary and seems alarming.
Also, the bolding and hyperlinking seems to be broken in the note : (
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.
Updated the link, hopefully it's fix that and the bolding issue... but definitely agree with @jas-kas that we should only have this show up in Angular.
<Alert level="warning"> | ||
We’re investigating possible performance degradation in some **Angular applications**. We recommend testing your application before releasing. Please reach out via [this GitHub ticket](https://github.com/getsentry/sentry-javascript/issues/6946) if you have issues. | ||
</Alert> | ||
|
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.
<Alert level="warning"> | |
We’re investigating possible performance degradation in some **Angular applications**. We recommend testing your application before releasing. Please reach out via [this GitHub ticket](https://github.com/getsentry/sentry-javascript/issues/6946) if you have issues. | |
</Alert> | |
<Alert level="warning"> | |
We’re investigating possible performance degradation in some **Angular applications**. We recommend testing your application before releasing. Please reach out via <a class href=“https://github.com/getsentry/sentry-javascript/issues/6946”>this GitHub ticket</a> if you have issues. | |
</Alert> | |
Links haven't been working in alerts/notes for some reason. ^^ they do seems to work if we write them this way.
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.
Ah looks like markdown is not supported inside of react components, thanks!
Uh oh!
There was an error while loading. Please reload this page.