fix: Rename internal SetupLogging
to SetupUnityLogging
#2096
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.
This PR renames the
internal
extension-methodSetupLogging
toSetupUnityLogging
on theSentryUnityOptions
.Context
With getsentry/sentry-dotnet#4026 and release
5.5.0
the Sentry .NET SDK made its internals visible to the Unity SDK. This causes the extension method to get skipped and instead ofsentry-unity/src/Sentry.Unity/SentryUnityOptionsExtensions.cs
Line 50 in 3e02634
the actual
SetupLogging
on theSentryOptions
gets called, creating aConsoleLogger
instead.#skip-changelog