Tags: luevano/libmangal
Tags
refactor(auth)!: moved all auth handling out of libmangal BREAKING CHANGE: remove all (for now only oauth was handled) auth handling from libmangal, this should be handled by "front end" clients such as `mangal`; all libmangal cares about is the access token, which is also no longer cached (or the user data) as mentioned in previous commits, this was bound to happen and i feel like this is the best way to use login from libmangal; need to decide if the User data should be cached, depending on how much the User data is being retrieved this might be needed
feat(anilist)!: add auth user anilist, heavily refactor auth BREAKING CHANGE: an username is needed to start an authenticated anilist and all authentication related methods are heavily modified - add anilist user data (for authenticated user) - change the way the auth data is saved, the username is now used as the key for storing the access token user data - change method for code grant and add implicit grant (access token), both validated by getting the authenticated user data - logout method now takes a parameter to let anilist now to delete the cached data or not - add method to delete username auth data
refactor(metadata)!: made the metadata a generalized interface BREAKING CHANGES: the metadata is now an interface and its behavior is heavily different; an generic implementation for providers is available as well as the anilist manga (which is metadata); this change will make it easier to develop metadata consumers (such as a UI to see the metadata) and just have to worry about one implementation for each usage of the metadata
PreviousNext