-
Notifications
You must be signed in to change notification settings - Fork 21
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
Need to introduce inheritance in spec to replace polymorphism in NumberVerificationRequestBody #48
Comments
I understand the issue. If the aim is to send one or the other, an alternative may be to define them as optional properties, indicating that one and only one is expected:
|
Hi @jlurien, |
If OK, I can do a PR |
Hi @jlurien it's ok for me |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem description
As PhoneNumber and HashedPhoneNumber don't extends NumberVerificationRequestBody a client using strongly typed language must have to serialize its request by hand.
Expected behavior
I want to be able to inject my PhoneNumber or HashedPhoneNumber as NumberVerificationRequestBody
Alternative solution
Additional context
This evolution is conform to PR #22 in commonallities
The text was updated successfully, but these errors were encountered: