Merged
Conversation
42ad450 to
8c7f464
Compare
Member
Author
|
I was attempting to validate the session token by fetching the language list but the language list fetch seems to work regardless of the session token being incorrect. So I'm looking for another way to validate the API key without causing actual compute on Kagi's end. Moving to draft state for now. |
2cdf4fa to
b4f4465
Compare
rafaelmardojai
approved these changes
Aug 27, 2025
This file contains hidden or 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
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.
Session token can be taken from Kagi settings and used for testing. Trial token should also work.
Most importantly, with this, we now support "Gen Z" as a language in Dialect.