Skip to content

Conversation

@krystofwoldrich
Copy link
Contributor

@krystofwoldrich krystofwoldrich commented May 23, 2024

📢 Type of change

  • New feature
  • Enhancement
  • Refactoring

📜 Description

💚 How did you test it?

  • sample app, unit tests

📝 Checklist

  • I reviewed submitted code
  • I added tests to verify changes
  • No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled
  • All tests passing
  • No breaking changes - JS V8

🔮 Next steps

  • Write down breaking changes
  • Add detailed changelog to the v6 branch
  • Fix E2E Tests

#skip-changelog

@github-actions
Copy link
Contributor

github-actions bot commented May 23, 2024

Messages
📖 Do not forget to update Sentry-docs with your feature once the pull request gets approved.

Generated by 🚫 dangerJS against f77a8fc

@github-actions
Copy link
Contributor

github-actions bot commented May 23, 2024

Android (legacy) Performance metrics 🚀

  Plain With Sentry Diff
Startup time 435.00 ms 470.11 ms 35.11 ms
Size 17.73 MiB 19.91 MiB 2.17 MiB

@krystofwoldrich krystofwoldrich changed the title Kw/js v8 upgrade feat(core): Bump sentry-javascript to version 8 May 23, 2024
@krystofwoldrich krystofwoldrich marked this pull request as ready for review May 23, 2024 18:17
@krystofwoldrich krystofwoldrich requested a review from mydea May 23, 2024 18:18
@krystofwoldrich krystofwoldrich requested a review from mydea May 27, 2024 18:46

const _createProfileEventFor = (profiledTransaction: Event): ProfileEvent | null => {
const profile_id = profiledTransaction?.contexts?.['profile']?.['profile_id'];
const profile_id = profiledTransaction?.contexts?.['trace']?.['data']?.['profile_id'];
Copy link
Collaborator

@lucas-zimerman lucas-zimerman May 28, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we refer to profiledTransaction as profiledEvent or profiledSpan since transactions are no longer used?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, make sense, I agree, but let's do it in another PR, to avoid adding more change to this, it's already a large PR.

Copy link
Member

@mydea mydea left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! 🚀

@github-actions
Copy link
Contributor

Android (new) Performance metrics 🚀

  Plain With Sentry Diff
Startup time 375.35 ms 383.34 ms 7.99 ms
Size 7.15 MiB 8.18 MiB 1.04 MiB

public init(): void {
super.init();
this._initNativeSdk();
super.init();
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Q: Was it previously wrong and you fix it now or is it a change that was required for V8?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The init was added for V8, the native init needs to happen before the JS init, to avoid the native not available error log in Expo.

Before v8 the native init happened in constructor, which doesn't make sense with dedicate init method.

Copy link
Collaborator

@lucas-zimerman lucas-zimerman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

a minor question but other than that LGTM!

@krystofwoldrich krystofwoldrich merged commit 666cd56 into v6 May 29, 2024
@krystofwoldrich krystofwoldrich deleted the kw/js-v8-upgrade branch May 29, 2024 07:55
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.

4 participants