Move V2.Event
API resources to V2.Core.Events
#1920
Merged
+49
−46
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?
In
2024-09-30.acacia
(docs), we released our new V2 Event system, found under the/v2/core/events
API endpoint. When we put them in our in SDKs, for presentation reasons, we put these new resources in theStripe.V2.Event
namespace.We've realized that dropping
Core
from the SDK namespace adds more confusion than good, so we're putting the v2Event
resource into theStripe.V2.Core
namespace, where you'd expect to find it in the first place.There's no change to specific event classes, like
V1BillingMeterErrorReportTriggeredEvent
. Those are, and will continue to be, underStripe.Events
.What?
V2.Events
toV2.Core.Events
Changelog
Event
,RelatedObject
, etc) fromStripe\V2
toStripe\V2\Core
. They now correctly match their API path and are in line with all other resources. To update your code:Stripe\Events\V1BillingMeterErrorReportTriggeredEvent
) haven't moved.