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
I identified an issue with the getSplitOptionsResponse schema where the property charge_remainder_fee was incorrectly typed as optional(nullable(string)). This was causing errors when interacting with the API, as the correct type should be optional(nullable(boolean)).
Problem
Property: charge_remainder_fee
Current Type: optional(nullable(string))
Expected Type: optional(nullable(boolean))
Steps to Reproduce:
Use the SDK to interact with the getSplitOptionsResponse.
Note that the charge_remainder_fee is returned or expected as a boolean, causing type errors with the current schema.
Proposed Solution:
I've submitted a pull request that corrects the type to optional(nullable(boolean)), along with adjustments to the related interfaces.
I identified an issue with the
getSplitOptionsResponse
schema where the propertycharge_remainder_fee
was incorrectly typed asoptional(nullable(string))
. This was causing errors when interacting with the API, as the correct type should beoptional(nullable(boolean))
.Problem
charge_remainder_fee
optional(nullable(string))
optional(nullable(boolean))
Steps to Reproduce:
Proposed Solution:
I've submitted a pull request that corrects the type to
optional(nullable(boolean))
, along with adjustments to the related interfaces.Pull Request Link: #36 - Fix incorrect type for charge_remainder_fee
The text was updated successfully, but these errors were encountered: