Fix incorrect type for charge_remainder_fee in getSplitOptionsResponse schema #36
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.
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))
.Changes made:
Schema update:
charge_remainder_fee
fromoptional(nullable(string))
tooptional(nullable(boolean))
in thegetSplitOptionsResponse
schema.Interface update:
These changes should align the SDK with the API's expected behavior, preventing the type errors that were occurring.
Please review and let me know if any further adjustments are needed. Thanks!