[agent-base] Allow for never relying on stack trace #170
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
During an HTTP request, if
opts.protocol
is set, then use that to determine thesecureEndpoint
value. Coupling that with an explicitly setagent.protocol
in the instance (essentially "locking" it for use with eitherhttp
orhttps
module), then the agent will never rely on the stack trace. By default it will still rely on the stack trace to allow for agent instances to be used with eitherhttp
orhttps
modules.Also moved the internal props to an object using a symbol, instead of relying on underscore props.
Fixes #158.