feature: api key settings section #197
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
geclos
force-pushed
the
feature/apikeys_settings
branch
from
b8f5604 to
7700844
Compare
geclos
force-pushed
the
feature/apikeys_settings
branch
from
7700844 to
927e543
Compare
|
|
||
| export async function destroyApiKey(apiKey: ApiKey, db = database) { | ||
| return Transaction.call(async (trx) => { | ||
| await trx.delete(apiKeys).where(eq(apiKeys.id, apiKey.id)) |
There was a problem hiding this comment.
You check in frontend. But in backend do we check if it's last API key?
There was a problem hiding this comment.
will add it a future pr
geclos
force-pushed
the
feature/apikeys_settings
branch
from
927e543 to
50011ef
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.