Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

feat: Expose more datascrubbing utils via cabi #464

Merged
merged 1 commit into from
Feb 14, 2020

Conversation

untitaker
Copy link
Member

No description provided.

@untitaker untitaker requested review from jan-auer and a team February 11, 2020 13:16
unsafe fn relay_convert_datascrubbing_config(
config: *const RelayStr
) -> Result<RelayStr> {
let config: DataScrubbingConfig = serde_json::from_str((*config).as_str())?;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: Nomicon prefers turbofish here :)

@untitaker untitaker merged commit e0b93e7 into master Feb 14, 2020
@untitaker untitaker deleted the feat/datascrubbing-cabi branch February 14, 2020 09:25
untitaker added a commit to getsentry/sentry that referenced this pull request Feb 19, 2020
Hard-depends on getsentry/relay#464 to make CI pass
Related: getsentry/relay#469

get_event_enhancers now runs before scrubbing, and get_event_preprocessors after. All of our stacktrace processing happens in enhancers and stacktrace plugins.

I am making the assumption here that sessionstack data should not be scrubbed.
priscilawebdev pushed a commit to getsentry/sentry that referenced this pull request Feb 20, 2020
Hard-depends on getsentry/relay#464 to make CI pass
Related: getsentry/relay#469

get_event_enhancers now runs before scrubbing, and get_event_preprocessors after. All of our stacktrace processing happens in enhancers and stacktrace plugins.

I am making the assumption here that sessionstack data should not be scrubbed.
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants