Skip to content

doc: Explain why we call performance.clear* #2480

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

Merged
merged 2 commits into from
Mar 9, 2020

Conversation

rhcarvalho
Copy link
Contributor

Helping our future selves to maintain the code.

@rhcarvalho rhcarvalho requested a review from HazAT March 9, 2020 12:51
@rhcarvalho rhcarvalho requested a review from kamilogorek as a code owner March 9, 2020 12:51
@getsentry-bot
Copy link
Contributor

Warnings
⚠️ Please add a changelog entry for your changes.
Messages
📖

@sentry/browser bundle gzip'ed minified size: (ES5: 16.7412 kB) (ES6: 15.7559 kB)

📖 ✅ TSLint passed

Generated by 🚫 dangerJS against 77a7844

@rhcarvalho
Copy link
Contributor Author

Several errors in BrowserStack apparently unrelated to the changes https://travis-ci.com/getsentry/sentry-javascript/jobs/296023306.

@rhcarvalho rhcarvalho merged commit cda040f into master Mar 9, 2020
@rhcarvalho rhcarvalho deleted the rhcarvalho/doc-clear-entries branch March 9, 2020 15:00
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.

3 participants