Move codeBundleId from configuration to non-public client property #548
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.
Goal
Removes the
codeBundleId
from the public API and ontoBugsnagClient
. This is because end-users do not need to set the value - it is required only for the React Native implementation, where it is set via JS.Changeset
codeBundleId
property fromBugsnagConfiguration
Bugsnag
to setcodeBundleId
onBugsnagClient
rather thanBugsnagConfiguration
BugsnagApp
andBugsnagAppWithState
now have constructor parameter forcodeBundleId
rather than relying onBugsnagConfiguration
BugsnagClient
so that whencodeBundleId
is set, the value is propagated to events + sessionsapp.codeBundleId
value when an OOM is detectedTests
Updated existing test coverage to supply
codeBundleId
fromClient
rather thanConfiguration