-
Notifications
You must be signed in to change notification settings - Fork 222
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
Fix newTracker typing to accurately return null or undefined (fix #1167) #1175
Fix newTracker typing to accurately return null or undefined (fix #1167) #1175
Conversation
BundleMonFiles added (6)
Total files change +95.17KB 0% Final result: ✅ View report in BundleMon website ➡️ |
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.
Looks good! I'm just wondering whether we can release this in v3 or should wait for v4. I know that it doesn't change the behaviour of the tracker, but the change in the type can cause some user code to produce typescript errors with handling the null or undefined that might have not been produced before. I think this could be considered a breaking as users would need to change how they use the result of newTracker()
. So my opinion is that we should release this in v4.
@matus-tomlein |
20ed72b
to
7f7b010
Compare
70bbdcc
to
444c184
Compare
7f7b010
to
b210872
Compare
444c184
to
51dc112
Compare
b210872
to
61e1d46
Compare
Fix correct typing issue for
newTracker
possibly returning:null
when a tracker is already initialized with the same tracker id.undefined
when we are not in a browser context.(close #1167)