-
-
Notifications
You must be signed in to change notification settings - Fork 366
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
Kavita+ Overhaul & New Changelog #3507
Merged
Merged
+15,523
−3,048
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
…e parts, to allow Kavita to have full control over the rendering ability.
…t the user with the changelog and force them to refresh to get the latest code. Also take care of any transloco hacks to clear cache.
Updated so changelog code can now fetch against GH and fill out the nightly releases from the latest stable. Caching needs to be reworked.
…e much faster and not hammer GH as much.
…te code from earlier which wasn't caching the installed version properly.
…hese weird locale issues.
…around Kavita+ Format stuff. More code cleanup. Match flow is plumbed, but needs some work.
…to correct bad matches.
…ixing the match and lining up the DTOs with K+.
…a+ license to the admin.
…some extra information around expiration, if on a supported version, and if the license is active or not. Added information around how to reset the license, changed up wording around delete. Some work is inflight, but overall, less calls to the backend, more streamlined api calls.
… user to overwrite it (aka reset then register). This should make for a much better experience.
…e data from the series and send to Kavita+ to get potential matches. The user selects from the list and Kavita will relink with the data and regenerate all scrobble events (plus remove all for the old match). I still need the ability to enter in a custom query (like an AL/MAL url), but basic flow is working.
…folder. While internal only, it makes navigation a lot easier for me.
…esn't have to service more requests than needed.
…t of Kavita so that Kavita can provide better experiences. Kavita will send 2 emails out for K+ tokens that are expiring. One at 5 weeks out and 1 once expired.
…robble events after 24 hours. Added an info variant to the confirm service.
Moved scrobble holds to it's own preference item to make it easier for a user to find it.
…ense and feels more natural.
… better experience. I will update all other tables with this slowly.
…atch/Fix Match flow will handle all of that.
Added a "Needs Manual Match" for when a series has a Scrobble error.
…hat are more complex to be addressed later in this PR during the cleanup and polish phase.
…ory triggerable by the user. I just need to find a place to put the button for a non-admin to trigger it.
…ker change instead. This globalization breaks getting any sort of language from the culture.
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.
This is a large PR with a massive overhaul to Kavita+'s integration in Kavita, outlined #2979.
The goal of this release is to streamline a lot of the management activities of Kavita+ via Kavita, while bringing some wishlist items from the community as well, like Want to Read Sync and a shorter scrobble window. For Kavita+ users, please test this out and provide feedback for me. This release is for you.
In other news, this release has a new changelog experience and CoverDB can now be pulled from for images (currently it contains some AL people and CV people). This is preliminary support while I figure out how to approach an automated experience. Feel free to submit new covers to the repo.
New License Screen
Matched Metadata
User Tokens
Email History
Scrobbling Token Expiring Email
Match Metadata
Token Unlock Message
Kavita+ Unlocked
New Changelog Experience
Added
Changed
Fixed