Closed aidanranney closed 9 months ago
Dug into this a bit more - it appears that this issue may stem from the default configuration no longer including the API version and trailing slash. [Although I don't have the full context behind this change]
Given that the path provided to Request.put_endpoint/2 in the resource modules and elsewhere includes the additional params, would this just be a matter of updating the documentation?
This issue has been automatically marked as "stale:discard". If this issue still relevant, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment.
Closing this issue after a prolonged period of inactivity. If this issue is still relevant, feel free to re-open the issue. Thank you!
Package Version
3.0.0
Are you using the latest version?
Steps to Reproduce
Since updating to 3.0.0, a request we're building ourselves with
stripity_stripe
is no longer successfully hitting the Stripe API when the endpoint is provided following the published documentation.v1
prefixExpected Result
A valid network response is returned when using the function as documented.
Actual Result
A network error is returned.
Since updating, providing an endpoint like
/v1/refunds
toStripe.Request.put_endpoint/2
will return a valid response from Stripe.