Hondana 3.4.7

An asynchronous wrapper around the MangaDex v5 API

Hondana 『本棚』

A lightweight and asynchronous wrapper around the MangaDex v5 API. You can see our stable docs here!

---

Important Notice

The MangaDex team have made great strides in implementing their OAuth2 authentication system, and as such have deprecated standard login flows (email/user and pass -> token). This means that any accounts created AFTER December 7th 2022 cannot use Hondana currently to authenticate. This also means for accounts created BEFORE the above date, you will also be unable to authenticate once the methods are fully removed, to which there is no set date at the time of writing this.

I have asked the staff about adding the Client Credentials OAuth2 workflow as this fits this library wrapper's auth needs, as currently it only supports Authorization Code flows which doesn't really work here, as it is more designed for static apps, not per-user apps. I have a WIP branch (feature/oauth2) that currently attempts to spawn a webserver to handle the Auth Code flow but it is less than ideal and rather fragile. I will keep this README updated and a project will be added on the GitHub page to mark progress.

---

Features

We are currently at 100% feature compliance with the API.

Notes

Authenticated endpoints

Sadly (thankfully?) I am not an author on MangaDex, meaning I cannot test the creation endpoints for things like scanlators, artists, authors, manga or chapters. I have followed the API guidelines to the letter for these, but they may not work.

Any help in testing them is greatly appreciated.

Upload & Creation

Following the above, I can only use the public test manga for upload testing. These are currently implemented and tested to the best of my ability.

Examples

Please take a look at the examples directory for working examples.

NOTE: More examples will follow as the library is developed.

Current caveats to note

• There are no API endpoints for Artist. It seems they are not differentiated from Author types except in name only.
  • I have separated them logically, but under the hood all Artists are Authors and their __eq__ reports as such.
• The tags and report reasons are locally cached since you must pass UUIDs to the api (and I do not think you're going to memorize those), there's a convenience method for updating the local cache as Client.update_tags and Client.update_report_reasons respectively.
  • I have added an example on how to do the above for tags.
  • To use these tags, you can see an example here.
• Settings related endpoints are not currently exposed. I have implemented their documented use, but I do not expect them to currently function.
  • Once this is exposed fully I will implement a richer interface.
• Currently, if there are any errors in a chapter upload process, the error key does not contain filenames or identifiable information on exactly what file failed upload.
  • This means that I locally compare the succeeded files with the ones missing from the full response payload. The examples have been updated with how to check for an error.
• Currently, the Client.my_chapter_read_history method will not work. It is disabled on MD's side due to an issue they had previously. If/when it is re-introduced the method will remain the same.

Further information/tidbits

• For a bit more clarity on a Chapter's readableAt vs publishAt, see this page on the MangaDex docs.
• A query with the include_future_updates bool set to True will include chapters that are pending release by scanlation groups on MangaDex, but which may be available on their sites.

Contributing

If you would like to contribute to Hondana, please take a look at the contributing guidelines and follow the procedure there.

If you have any question please feel free to join my Discord server: