-
-
Notifications
You must be signed in to change notification settings - Fork 200
feat: add runtime API to query user consent requirement #1443
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
Conversation
|
| return rv; | ||
| } | ||
|
|
||
| int |
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.
int needed or we could use bool here? require_user_consent is a boolean.
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.
The existing public API uses int for similar boolean-style returns so the idea was just to keep it consistent.
JoshuaMoelans
left a comment
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.
LGTM!
This PR adds a new public API function
sentry_user_consent_is_required()that allows applications to query at runtime whether user consent is required. This complements the existing consent management APIs and addresses a gap where the consent requirement could only be queried during initialization with direct access to the options object.Closes #1441