Skip to content

fix: expose iteratee and update deprecated integrations#34

Open
canmertc wants to merge 1 commit into
nativescript-community:masterfrom
canmertc:fix/expose_iteratee
Open

fix: expose iteratee and update deprecated integrations#34
canmertc wants to merge 1 commit into
nativescript-community:masterfrom
canmertc:fix/expose_iteratee

Conversation

@canmertc
Copy link
Copy Markdown

Issue

There was some logic in client.ts, wrapper.android.ts, and wrapper.ios.ts that used to access iteratee via the integration object. So removing the _iteratee assignment in #33 broke this link while passing iteratee to the RewriteFrames constructor fixed the missing source snippet issue for the native errors and captureException calls.

Fix

Exported frame iteratee as frameIteratee. Replaced rewriteFrameIntegration._iteratee with direct frameIteratee(...) so the stacks can be rewritten without reaching into integration internals.

Adopted the newer @sentry/integrations factory exports (rewriteFramesIntegration, httpClientIntegration) as the RewriteFrames, and HttpClient are deprecated.

Refactor Sentry integrations to expose the frame iteratee as frameIteratee and adopt the newer @sentry/integrations factory exports (rewriteFramesIntegration, httpClientIntegration). Replace internal calls to rewriteFrameIntegration._iteratee with direct frameIteratee(...) invocations across client.ts, wrapper.android.ts, and wrapper.ios.ts so native JS stacks can be rewritten without reaching into integration internals.
Copy link
Copy Markdown
Member

@farfromrefug farfromrefug left a comment

Choose a reason for hiding this comment

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

Nice did you test your changes with http integration too?

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