Repository navigation
feat(trackers): manage reading tracker accounts and series links - #1303
Merged
Merged
Conversation
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.
What
Why
kmrs hosts per-user reading tracker integrations. KMReader can now manage those existing accounts and bindings without storing provider tokens or duplicating the server's automatic progress-sync logic.
Native OAuth is deliberately not included: the current kmrs callback requires a browser session, so disconnected providers link to
/account/trackerson the current server rather than sending the app's API key through a web flow.Validation
make formatmake build— iOS, macOS, and tvOS passed.make localizeandmisc/translate.py list— all 52 new strings translated, no missing translations.Includes
make bumpto build 667.🤖 Generated with Claude Code