-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
fix(native): update sentry_value_t
example with 64-bit integer types
#14509
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 3 commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
20c84bf
update `sentry_value_t` example with 64-bit integer types
JoshuaMoelans 2342093
add example to SDK usage page
JoshuaMoelans 4385de3
revert changes on capture-message
JoshuaMoelans c436b41
cleanup
JoshuaMoelans b58f3f2
add example `sentry_value_t` usage for setting context
JoshuaMoelans ea2a8f3
add note on uint64 string conversion
JoshuaMoelans File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we mention that 64-bit unsigned values get sent as Strings until further notice? For context, see getsentry/sentry-native#1326 (comment) . Not sure how relevant this is for most users.
e.g. add something like
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's a good idea to mention it (see below why), but I'd probably rephrase it:
wdyt?
why mention it at all: as we just discussed offline, data properties can be searched, and (un)signed int64 values will show up as both number (int64) and string (uint64) keys, this means that the actual user experience differs for unsigned int64 values