search

beam-community / stripity-stripe

An Elixir Library for Stripe
Other
985 stars 353 forks source link

Update OpenAPI spec file #849

Closed embarggo closed 2 weeks ago

embarggo commented 3 months ago

Problem Statement

I wanted to use the newer controller properties when creating an account with Stripe.Account.create but currently I get a Dialyzer warning because controller isn't a property for that function call. If we compare the account create operation (operationId PostAccounts) in the spec file for stripity_stripe with the latest official stripe spec file we can see that the controller property exists in the one but not the other.

Solution Brainstorm

I'd be glad to copy just the PostAccounts section from the official spec into this repo's spec file and make a PR, but I'm sure there are other updates to the spec as well that we may want to pull in. Let me know how I can help resolve this.

github-actions[bot] commented 2 months ago

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.

embarggo commented 2 months ago

I don't think this should be marked stale, as the problem still persists

yordis commented 2 months ago

I am on vacation, so I havent be able to get to https://github.com/beam-community/stripity-stripe/pull/853

I will encourage you to contribute

github-actions[bot] commented 1 month ago

This issue has been automatically marked as "stale:discard". We are sorry that we haven't been able to prioritize it yet. If this issue still relevant, please leave any comment if you have any new additional information that helps to solve this issue. We encourage you to create a pull request, if you can. We are happy to help you with that.

github-actions[bot] commented 2 weeks ago

Closing this issue after a prolonged period of inactivity. If this issue is still relevant, feel free to re-open the issue. Thank you!