Remove Upcoming Lines API from SDK#3064
Merged
jar-stripe merged 2 commits intomasterfrom Mar 14, 2025
Merged
Conversation
modified manually maintained code to remove methods that referenced this service removed broken tests
jar-stripe
changed the title
Contributor
Author
|
This PR also adds |
mbroshi-stripe
approved these changes
Mar 14, 2025
ramya-stripe
added a commit
that referenced
this pull request
Mar 19, 2025
* add codeowners file (#3055) * Improved examples (#3054) * changed Program to accept a command line argument with the name (relative to Examples namespace) of the example to run * updated existing examples * added usage instructions * added just recipe * Update generated code (#3050) * Update generated code for v1463 * Update generated code for v1494 * Update generated code for v1495 * Update generated code for v1501 * Update generated code for v1505 --------- Co-authored-by: Stripe OpenAPI <105521251+stripe-openapi[bot]@users.noreply.github.com> Co-authored-by: prathmesh-stripe <165320323+prathmesh-stripe@users.noreply.github.com> * Bump version to 47.4.0 * Remove Upcoming Lines API from SDK (#3064) * Revert changes to v2 apis --------- Co-authored-by: David Brownman <109395161+xavdid-stripe@users.noreply.github.com> Co-authored-by: jar-stripe <jar@stripe.com> Co-authored-by: stripe-openapi[bot] <105521251+stripe-openapi[bot]@users.noreply.github.com> Co-authored-by: Ramya Rao <ramya@stripe.com>
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
2 participants
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.
Why?
The stripe-dotnet SDK has some deprecated methods that referenced the /v1/invoices/upcoming and /v1/invoices/upcoming/lines APIs. These APIs are scheduled for removal in the upcoming version. This PR removes the deprecated methods in preparation for the upcoming change
What?
This PR also updates the description for the EventDestinations resource.
Changelog
InvoiceUpcomingLinesServiceand all dependent objects.UpcomingLinesproperty inInvoiceService, and theListUpcomingLineItems,ListUpcomingLineItemsAsync,ListUpcomingLineItemsAutoPaging,ListUpcomingLineItemsAutoPagingAsync,UpcomingLines,UpcomingLinesAsync,UpcomingLinesAutoPaging, andUpcomingLinesAutoPagingAsyncmethods fromInvoiceService. UseCreatePrevieworCreatePreviewAsyncto create a preview invoice and then use existing InvoiceService methods with the preview invoice ID (see https://docs.stripe.com/invoicing/preview).CreatedGt,CreatedGte,CreatedLt,CreatedLte, andDeliverySuccessfilter options toStripe.V2.Core.EventListOptions.