Closed ithielnor closed 7 years ago
It's actually two separate objects in our backend. We use Scala so for the Update, many of the fields are Option[String] vs String for Create. Additionally, Update can take a Status property for suspending or deactivating a customer. We use Swagger to auto-generate this page but the generated clients were pretty ugly. I started down the path to auto-generate at least the models from the Swagger JSON, but other things have come up.
I didn't realize CreateCustomerRequest already has Status
, it shouldn't. I removed it and created an UpdateCustomerRequest
It looks like Update Customer accepts the same properties as Create Customer (at least for an unverified customer). Should there be a
UpdateCustomerRequest
model or should we just use theCreateCustomRequest
. If the latter, I suggest renaming it.