Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update OpenAPI spec file #849

Open
embarggo opened this issue Aug 3, 2024 · 4 comments
Open

Update OpenAPI spec file #849

embarggo opened this issue Aug 3, 2024 · 4 comments

Comments

@embarggo
Copy link

embarggo commented Aug 3, 2024

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.

Copy link

github-actions bot commented Sep 3, 2024

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
Copy link
Author

embarggo commented Sep 6, 2024

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

@yordis
Copy link
Member

yordis commented Sep 7, 2024

I am on vacation, so I havent be able to get to #853

I will encourage you to contribute

Copy link

github-actions bot commented Oct 8, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants