fix(billing): Add missing invoice and billing details proto fields#232
Closed
fix(billing): Add missing invoice and billing details proto fields#232
Conversation
|
The latest Buf updates on your PR. Results from workflow ci / buf-checks (pull_request).
|
16d57ca to
ae39ce8
Compare
ae39ce8 to
b0dc7f1
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add the missing billing contract fields that getsentry already constructs in Python so generated stubs and runtime usage stay aligned.
Invoice Schema Alignment
Invoicenow includesorganization_id,paid,date_added, andguid, matching constructor kwargs used by getsentry contract/invoicer services.Billing Details Schema Alignment
BillingDetailsnow includesdisplay_address,billing_email, andcompany_name, matching kwargs used by the billing details service response mapping.Made with Cursor