Skip to content

Commit

Permalink
Update generated code for v1099
Browse files Browse the repository at this point in the history
  • Loading branch information
stripe-openapi[bot] committed Jun 25, 2024
1 parent 345499a commit 02a9392
Show file tree
Hide file tree
Showing 4 changed files with 6 additions and 6 deletions.
2 changes: 1 addition & 1 deletion OPENAPI_VERSION
Original file line number Diff line number Diff line change
@@ -1 +1 @@
v1097
v1099
2 changes: 1 addition & 1 deletion stripe/_capability.py
Original file line number Diff line number Diff line change
Expand Up @@ -160,7 +160,7 @@ class Error(StripeObject):
]
]
"""
This is typed as a string for consistency with `requirements.disabled_reason`, but it safe to assume `future_requirements.disabled_reason` is empty because fields in `future_requirements` will never disable the account.
This is typed as an enum for consistency with `requirements.disabled_reason`, but it safe to assume `future_requirements.disabled_reason` is null because fields in `future_requirements` will never disable the account.
"""
errors: List[Error]
"""
Expand Down
4 changes: 2 additions & 2 deletions stripe/billing/_meter.py
Original file line number Diff line number Diff line change
Expand Up @@ -148,9 +148,9 @@ class ListEventSummariesParams(RequestOptions):
"""
A cursor for use in pagination. `starting_after` is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, ending with `obj_foo`, your subsequent call can include `starting_after=obj_foo` in order to fetch the next page of the list.
"""
value_grouping_window: NotRequired[Literal["hour"]]
value_grouping_window: NotRequired[Literal["day", "hour"]]
"""
Specifies what granularity to use when generating event summaries. If not specified, a single event summary would be returned for the specified time range.
Specifies what granularity to use when generating event summaries. If not specified, a single event summary would be returned for the specified time range. For hourly granularity, start and end times must align with hour boundaries (e.g., 00:00, 01:00, ..., 23:00). For daily granularity, start and end times must align with UTC day boundaries (00:00 UTC).
"""

class ListParams(RequestOptions):
Expand Down
4 changes: 2 additions & 2 deletions stripe/billing/_meter_event_summary_service.py
Original file line number Diff line number Diff line change
Expand Up @@ -39,9 +39,9 @@ class ListParams(TypedDict):
"""
A cursor for use in pagination. `starting_after` is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, ending with `obj_foo`, your subsequent call can include `starting_after=obj_foo` in order to fetch the next page of the list.
"""
value_grouping_window: NotRequired[Literal["hour"]]
value_grouping_window: NotRequired[Literal["day", "hour"]]
"""
Specifies what granularity to use when generating event summaries. If not specified, a single event summary would be returned for the specified time range.
Specifies what granularity to use when generating event summaries. If not specified, a single event summary would be returned for the specified time range. For hourly granularity, start and end times must align with hour boundaries (e.g., 00:00, 01:00, ..., 23:00). For daily granularity, start and end times must align with UTC day boundaries (00:00 UTC).
"""

def list(
Expand Down

0 comments on commit 02a9392

Please sign in to comment.