-
Notifications
You must be signed in to change notification settings - Fork 0
added client signature functionality #55
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
Conversation
moeodeh3
left a comment
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.
looks great - just some small nits, really appreciate you taking this on 🐐
| packages: | ||
| stamper: patch | ||
| changelog: |- | ||
| Added a `sign` function to the Api Key Stamper for signing client signatures and such. |
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.
Added a sign function to the API Key Stamper for signing arbitrary payloads
| http: patch | ||
| types: patch | ||
| changelog: |- | ||
| Synced `types` and `http client` with v2025.12.2 of `mono` |
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.
Synced com.turnkey.types and com.turnkey.http with v2025.12.2 of mono
| } | ||
| } | ||
|
|
||
| fun decodeVerificationToken(verificationToken: String): VerificationToken { |
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 feel like these should be public methods, not internal
if someone wants to use their own backend and generate client signatures themselves, these functions would make that much easier!
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 internal directory doesn't really mean anything in Kotlin, the method is still public for anyone to use so shouldn't be an issue.
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.
okay sweet - however, this is a bit misleading for readers. Eventually we should restructure this to clearly separate internal vs. public
that said, this is out of scope for this PR, so I’m going to mark it as resolved
| } | ||
| } | ||
|
|
||
| fun decodeVerificationToken(verificationToken: String): VerificationToken { |
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.
okay sweet - however, this is a bit misleading for readers. Eventually we should restructure this to clearly separate internal vs. public
that said, this is out of scope for this PR, so I’m going to mark it as resolved
No description provided.