ref: Expose configurable stack parser#4902
Conversation
Removes all references to `@sentry/apm`, a deprecated package we do not use anymore.
Removes the deprecated `API` class.
Removes `getActiveDomain` function and corresponding type.
The `user` dsn component was renamed to `publicKey`. This PR removes that from the dsn field.
…ntOutgoingRequests (getsentry#4859)
Increases the creation timeout of `MongoMemoryServer` to temporarily fix Node integration test flakiness
This PR removes the previously deprecated `frameContextLines` from `NodeOptions`.
…4887) These exports were historically used in `@sentry/electron`, but are no longer being used by the Electron SDK or the React Native SDK, so they can be removed.
|
We'll do this for node as well right? |
318e093 to
0988600
Compare
|
I'm gonna hold off on this as we are prepping our first alpha: #4892 Let's get this in alongside the decision about |
|
@timfish let's wait until we get the backend deletion changes merged in first, it'll minimize merge conflicts and maybe make things cleaner here. |
|
Deleting the backend (#4919) merged in, I think we can rebase on top of that and make changes as appropriate. Sorry for the rebase trouble! |
No trouble at all! All rebased and fixed and ready to review. Do you think this approach is still good after the backend delete? |
AbhiPrasad
left a comment
There was a problem hiding this comment.
My only qualm with this approach is:
Whenever we want access to a StackParser to use with the functions in eventbuilder we call stackParserFromOptions(options). This converts StackLineParser[] to StackParser and saves it back in the options so this conversion only occurs once.
I think we want to move toward a world where we have two sets of options, the top level init one's and the internal client options. This also means the top level init options becomes immutable, which I think fits user mental models better.
Let's think about that after this PR gets merged in though! I'm going to start work on default integrations, so I can take a look at the options more holistically.
Adds a `stackParser` option to `Options`: ```ts /** * A stack parser implementation or an array of stack line parsers * By default, a stack parser is supplied for all supported browsers */ stackParser?: StackParser | StackLineParser[]; ``` Whenever we want access to a `StackParser` to use with the functions in `eventbuilder` we call `stackParserFromOptions(options)`. This converts `StackLineParser[]` to `StackParser` and saves it back in the options so this conversion only occurs once. ### Added Exports `@sentry/node` - `nodeStackParser` `@sentry/browser` - `chromeStackParser` - `geckoStackParser` - `opera10StackParser` - `opera11StackParser` - `winjsStackParser` - `defaultStackParsers`
Adds a `stackParser` option to `Options`: ```ts /** * A stack parser implementation or an array of stack line parsers * By default, a stack parser is supplied for all supported browsers */ stackParser?: StackParser | StackLineParser[]; ``` Whenever we want access to a `StackParser` to use with the functions in `eventbuilder` we call `stackParserFromOptions(options)`. This converts `StackLineParser[]` to `StackParser` and saves it back in the options so this conversion only occurs once. ### Added Exports `@sentry/node` - `nodeStackParser` `@sentry/browser` - `chromeStackParser` - `geckoStackParser` - `opera10StackParser` - `opera11StackParser` - `winjsStackParser` - `defaultStackParsers`
Adds a `stackParser` option to `Options`: ```ts /** * A stack parser implementation or an array of stack line parsers * By default, a stack parser is supplied for all supported browsers */ stackParser?: StackParser | StackLineParser[]; ``` Whenever we want access to a `StackParser` to use with the functions in `eventbuilder` we call `stackParserFromOptions(options)`. This converts `StackLineParser[]` to `StackParser` and saves it back in the options so this conversion only occurs once. ### Added Exports `@sentry/node` - `nodeStackParser` `@sentry/browser` - `chromeStackParser` - `geckoStackParser` - `opera10StackParser` - `opera11StackParser` - `winjsStackParser` - `defaultStackParsers`
Adds a `stackParser` option to `Options`: ```ts /** * A stack parser implementation or an array of stack line parsers * By default, a stack parser is supplied for all supported browsers */ stackParser?: StackParser | StackLineParser[]; ``` Whenever we want access to a `StackParser` to use with the functions in `eventbuilder` we call `stackParserFromOptions(options)`. This converts `StackLineParser[]` to `StackParser` and saves it back in the options so this conversion only occurs once. ### Added Exports `@sentry/node` - `nodeStackParser` `@sentry/browser` - `chromeStackParser` - `geckoStackParser` - `opera10StackParser` - `opera11StackParser` - `winjsStackParser` - `defaultStackParsers`
Adds a `stackParser` option to `Options`: ```ts /** * A stack parser implementation or an array of stack line parsers * By default, a stack parser is supplied for all supported browsers */ stackParser?: StackParser | StackLineParser[]; ``` Whenever we want access to a `StackParser` to use with the functions in `eventbuilder` we call `stackParserFromOptions(options)`. This converts `StackLineParser[]` to `StackParser` and saves it back in the options so this conversion only occurs once. ### Added Exports `@sentry/node` - `nodeStackParser` `@sentry/browser` - `chromeStackParser` - `geckoStackParser` - `opera10StackParser` - `opera11StackParser` - `winjsStackParser` - `defaultStackParsers`
Adds a
stackParseroption toOptions:Whenever we want access to a
StackParserto use with the functions ineventbuilderwe callstackParserFromOptions(options). This convertsStackLineParser[]toStackParserand saves it back in the options so this conversion only occurs once.Added Exports
@sentry/nodenodeStackParser@sentry/browserchromeStackParsergeckoStackParseropera10StackParseropera11StackParserwinjsStackParserdefaultStackParsers