You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I asked to support developers on Discord about how to disable the billing threshold from the SubscriptionSchedulePhaseItemParams struct. The documentation said you have to pass an empty string in order to disable it. I've tried to pass an empty SubscriptionSchedulePhaseItemParams struct or pass nil but it didn't work.
Finally the solution they gave me is to set manually the empty string using the .AddExtra() method and pass it like this: phases[1][billing_thresholds]
Describe the solution you'd like
I would like to passing nil or the empty SubscriptionSchedulePhaseItemParams struct should disable the billing threshold.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
We'll look into into strongly-typed ways of clearing fields.
pakrym-stripe
changed the title
Adapt struct SubscriptionSchedulePhaseItemParams to incorporate empty string in order to disable the billing threshold
Provide a strongly-typed way of clearing fields on update
Feb 8, 2023
Is your feature request related to a problem? Please describe.
I asked to support developers on Discord about how to disable the billing threshold from the SubscriptionSchedulePhaseItemParams struct. The documentation said you have to pass an empty string in order to disable it. I've tried to pass an empty SubscriptionSchedulePhaseItemParams struct or pass nil but it didn't work.
Finally the solution they gave me is to set manually the empty string using the .AddExtra() method and pass it like this: phases[1][billing_thresholds]
Describe the solution you'd like
I would like to passing nil or the empty SubscriptionSchedulePhaseItemParams struct should disable the billing threshold.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: