-
Notifications
You must be signed in to change notification settings - Fork 22
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
nicolas/dash 329 dapi delete ability to delete passkey #320
nicolas/dash 329 dapi delete ability to delete passkey #320
Conversation
505d6dc
to
3445b5e
Compare
Co-authored-by: Kevin Wang <[email protected]>
Co-authored-by: Kevin Wang <[email protected]>
}, | ||
} | ||
client := NewClient(config) | ||
passkey, err := client.DeletePasskey(context.Background(), userID, passkeyIdentificationID) |
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.
❓ Do we need to seed a passkey?
What happens if we call client.DeletePasskey
twice in this test?
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.
the test only asserts the http call for BAPI through the transporter. Defined 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.
I see, so Out
is effectively the mocked-expected-response
This PR implements a new method from a new BAPI endpoint to delete passkeys. It's all under the users' client.