Adopt generic variant type in public APIs #971
Draft
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
Instructions and example for changelogPlease add an entry to Example: ## Unreleased
- Adopt generic variant type in public APIs ([#971](https://github.com/getsentry/sentry-unreal/pull/971))If none of the above apply, you can opt out of this check by adding |
tustanivsky
changed the title
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.
This PR adopts the
FSentryVarianttype introduced in #940 for use in public APIs that handle arbitrary Sentry objects data (e.g. contexts and extras inUSentryScope, data inUSentryBreadcrumb). This allows to move away from usingFStringin favor of a more flexible and type-safe approach.It also adds TryGet-functions for scope's tags, extras and contexts (#951).