-
Notifications
You must be signed in to change notification settings - Fork 15
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
Changes from gocardless-dotnet-template #66
Conversation
6f23b09
to
200eff5
Compare
/// An array of fields which are missing and is required to set up the | ||
/// mandate. | ||
/// </summary> | ||
public class PayerAuthorisationIncompleteField |
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.
Why is this in singular? I guess it just messed with the summary - maybe because the description is empty
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.
I think singular is fine here as its plural in where it's used:
public List<PayerAuthorisationIncompleteField> IncompleteFields { get; set; }
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.
LGTM, but would like to have someone from @gocardless/mme-experience to take a look too before merging. Maybe @lancscoder who's got more experience with .NET?
This is our new API dedicated to building custom payment pages. It encapsulates the creation of customer, bank account and mandate under this single resource.
298ee5b
to
fb4da36
Compare
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.
LGTM 👍
/// An array of fields which are missing and is required to set up the | ||
/// mandate. | ||
/// </summary> | ||
public class PayerAuthorisationIncompleteField |
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.
I think singular is fine here as its plural in where it's used:
public List<PayerAuthorisationIncompleteField> IncompleteFields { get; set; }
Updating client libraries as part of PayerAuthorisation API launch