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
{{ message }}
This repository was archived by the owner on Nov 26, 2024. It is now read-only.
I have sent the issues below to the Paddle support, and this is on hold until they respond (and hopefully improve things).
1. The documentation changed from JSON schemas to markdown
Parsing markdown tables & manually typed text is possible, but it makes it harder than it needs to be, and needs a bunch of random hacks to get around inconsistencies.
2. The documentation is incorrect in large parts
generate-pay-link shows request.prices is a string. It should be an Array<string> | string
list-users is missing response.quantity in the schema. It is shown in the example response and should be an integer?.
list-users is showing response.next_payment as an object. It should be an object?.
I'm sure there are plenty more examples - those are just the ones I found in the first few endpoints I looked at, not even checking against the API. Without trying it out, there is currently no way of knowing what the API expects or responds with.
The text was updated successfully, but these errors were encountered:
WIP branch: https://github.com/devoxa/paddle-sdk/tree/fix-generators
On hold
I have sent the issues below to the Paddle support, and this is on hold until they respond (and hopefully improve things).
1. The documentation changed from JSON schemas to markdown
Parsing markdown tables & manually typed text is possible, but it makes it harder than it needs to be, and needs a bunch of random hacks to get around inconsistencies.
2. The documentation is incorrect in large parts
request.prices
is astring
. It should be anArray<string> | string
response.quantity
in the schema. It is shown in the example response and should be aninteger?
.response.next_payment
as anobject
. It should be anobject?
.alert_id
when it's actually foralert_name
.I'm sure there are plenty more examples - those are just the ones I found in the first few endpoints I looked at, not even checking against the API. Without trying it out, there is currently no way of knowing what the API expects or responds with.
The text was updated successfully, but these errors were encountered: