Init() to support runtime addition of Bugsnag component to existing GameObject #34
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…an existing object and initialized at runtime with a variable key instead of one set through the Inspector.
|
Thanks for the contribution @TimothyKLambert, this looks good! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I created a public Init() method so the Bugsnag component can be added to an existing GameObject and initialized at runtime with a variable API key instead of predefined set through the Inspector.
We need this for our SDK because we support multiple API keys that can change for each project that uses our SDK so having to set the API key through the inspector before hand breaks our integration flow.