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

Add support for spending_limits with Issuing Card and Cardholder #831

Merged
merged 1 commit into from
Apr 12, 2019

Conversation

remi-stripe
Copy link
Contributor

r? @brandur-stripe
cc @stripe/api-libraries @zacht-stripe

Copy link
Contributor

@brandur-stripe brandur-stripe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks Remi!

Categories []*string `form:"categories"`
Interval *string `form:"interval"`
}

// AuthorizationControlsParams is the set of parameters that can be used for the shipping parameter.
type AuthorizationControlsParams struct {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For some reason I never prefixed this with Issuing. Do you agree it's better to rename in the next major? (there will be an API version).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I noticed that too. Yeah, I think it's fine to just wait for the next major.


// The following parameters are considered deprecated and only apply to issuing cards
MaxAmount *int64 `form:"max_amount"`
MaxApprovals *int64 `form:"max_approvals"`
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doing this as this is going away in a future API version and is technically unsupported on Cardholder

// IssuingCardAuthorizationControls is the resource representing authorization controls on an issuing card.
// TODO: Rename to IssuingAuthorizationControls in the next major
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Flagging this as I am using the bad class name in Cardholder. An API version will be released to change this so I wanted to avoid 2 major versions

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1.

@remi-stripe
Copy link
Contributor Author

@brandur-stripe Thanks for the review! For some reason I forgot to post my review/comments after I was done yesterday. Any chance you could have a quick look?

@brandur-stripe
Copy link
Contributor

Thanks for the additional flavor Remi — I'm in agreement on waiting for the next major and just having the TODO for now. LGTM.

@remi-stripe remi-stripe merged commit b1f7098 into master Apr 12, 2019
@remi-stripe remi-stripe deleted the remi-issuing-authorization-controls branch April 12, 2019 22:05
nadaismail-stripe pushed a commit that referenced this pull request Oct 18, 2024
Bumps [sequel](https://github.com/jeremyevans/sequel) from 5.60.1 to 5.61.0.
- [Release notes](https://github.com/jeremyevans/sequel/releases)
- [Changelog](https://github.com/jeremyevans/sequel/blob/master/CHANGELOG)
- [Commits](jeremyevans/sequel@5.60.1...5.61.0)

---
updated-dependencies:
- dependency-name: sequel
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants