Skip to content
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

refactor: Extract Details message type definitions in Kingdom internal API #1798

Merged
merged 1 commit into from
Sep 11, 2024

Conversation

SanjayVas
Copy link
Member

The Details messages are persisted in the underlying Spanner database. Extracting them simplifies the migration to native protobuf types in Cloud Spanner.

This change maintains binary compatibility for all existing serialized message types.

@wfa-reviewable
Copy link

This change is Reviewable

…l API

The Details messages are persisted in the underlying Spanner database. Extracting them simplifies the migration to native protobuf types in Cloud Spanner.

This change maintains binary compatibility for all existing serialized message types.
Copy link
Collaborator

@stevenwarejones stevenwarejones left a comment

Choose a reason for hiding this comment

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

Reviewed 95 of 95 files at r1, all commit messages.
Reviewable status: :shipit: complete! all files reviewed, all discussions resolved (waiting on @SanjayVas)

@SanjayVas SanjayVas merged commit 552febb into main Sep 11, 2024
4 checks passed
@SanjayVas SanjayVas deleted the sanjayvas-details-proto branch September 11, 2024 16:19
roaminggypsy pushed a commit that referenced this pull request Sep 13, 2024
…l API (#1798)

The Details messages are persisted in the underlying Spanner database. Extracting them simplifies the migration to native protobuf types in Cloud Spanner.

This change maintains binary compatibility for all existing serialized message types.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants