-
Notifications
You must be signed in to change notification settings - Fork 354
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
add shared options to documentation #452
Conversation
1 similar comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One item for feedback but this seems like a great addition!
lib/stripe.ex
Outdated
* `:api_key` - The Stripe API key to use for the request. See | ||
[https://stripe.com/docs/api/authentication](https://stripe.com/docs/api/authentication) | ||
* `:connect_account` - A Stripe Connect account ID which should originate | ||
the specified action using the "Stripe-Account" header. The preferred |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should originate the specified action
- any different wording that could be applied here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just updated this. What do you think of the new one?
* `:connect_account` - The ID of a Stripe Connect account for which the
request should be made, passed through as the "Stripe-Account" header. The
preferred authentication method for Stripe Connect. See
[https://stripe.com/docs/connect/authentication#stripe-account-header](https://stripe.com/docs/connect/authentication#stripe-account-header)
Similar to #441 I had a hard time figuring out how to create a charge on a connected account using the
Stripe-Account
header. Because of that, I submit that documentation around available options should be added. I'd love feedback on exactly where to put that documentation, but I think since it's available in almost every function it should be at a high level.This PR will add a section to the
Stripe
docs that looks like this: