-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
meta: 7.0.0-beta.0 CHANGELOG #5011
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
size-limit report 📦
|
7327b64 to
1ff254e
Compare
1ff254e to
7854fa1
Compare
|
Blocked by #5015 |
MIGRATION.md
Outdated
| import { stackParserFromOptions } from '@sentry/utils'; | ||
|
|
||
| // New in v7: | ||
| const client = BrowserClient({ |
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.
I would be careful using PascalCase naming when the intention is doing a function call.
It is easy to miss that they are technically functions and assume that they are constructors and people adding new BrowserClient(...). And the worst is that it is "technically correct" from the perspective of the runtime (but wrong based on the usage, and intention).
I will recommend to do makeBrowserClient or browserClient or newBrowserClient but avoid PascalCase.
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.
yup, this is my bad. BrowserClient is still a class for now - so there should be the new keyword here - we'll maybe revisit this at a later time though,
Co-authored-by: Luca Forstner <[email protected]>
CHANGELOG for the v7 beta!