Skip to content

fix(relocation): Clean up relocation serializer #71930

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 1 commit into from
Jun 4, 2024

Conversation

azaslavsky
Copy link
Contributor

@azaslavsky azaslavsky commented Jun 3, 2024

This is part of a series of changes to fix
SENTRY-38N6. This is change 2 of 4:

1. Add new API to client in getsentry
2. Add new API to server in sentry <- THIS CHANGE
3. Remove old API, and only use new one, in getsentry
4. Remove old API from server in sentry

This change extends the serializer to support both the new style of nested creator/owner objects, and the old, deprecated style.

Fixes SENTRY-38N6.

This is part of a series of changes to fix
[SENTRY-38N6](https://sentry.sentry.io/issues/5282819613/). This is
change 2 of 4:

1. Add new API to client in getsentry
2. Add new API to server in sentry <- THIS CHANGE
3. Remove old API from client in getsentry
4. Remove old API from server in sentry.

This change extends the serializer to support both the new style of
nested `creator`/`owner` objects, and the old, deprecated style.

Fixes [SENTRY-38N6](https://sentry.sentry.io/issues/5282819613/).
@azaslavsky azaslavsky marked this pull request as ready for review June 3, 2024 18:56
@azaslavsky azaslavsky enabled auto-merge (squash) June 3, 2024 18:57
@azaslavsky azaslavsky requested a review from hubertdeng123 June 3, 2024 18:57
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Jun 3, 2024
@azaslavsky azaslavsky disabled auto-merge June 3, 2024 22:26
@azaslavsky azaslavsky merged commit b08baa5 into master Jun 4, 2024
50 checks passed
@azaslavsky azaslavsky deleted the azaslavsky/cleanup-relocation-serializer branch June 4, 2024 18:46
azaslavsky added a commit that referenced this pull request Jun 5, 2024
This is part of a series of changes to fix
[SENTRY-38N6](https://sentry.sentry.io/issues/5282819613/). This is
change 4 of 4:

[1](https://github.com/getsentry/getsentry/pull/14166). Add a new API to
client in getsentry
[2](#71930). Add new API to
server in sentry
[3](https://github.com/getsentry/getsentry/pull/14169). Remove old API,
and only use new one, in getsentry
4. Remove old API from server in sentry <- THIS CHANGE

Now that all clients that rely on this serializer only use new fields,
we can go ahead and remove the old, flattened versions.
@github-actions github-actions bot locked and limited conversation to collaborators Jun 20, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Scope: Backend Automatically applied to PRs that change backend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants