You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This option would allow users to fix the few edge cases where the server doesn't detect the proper cover image in the archive.
This doesn't necessarily need an API endpoint and could just be glued to the Reader Controller class, but being a good host to third-party clients is important!
The text was updated successfully, but these errors were encountered:
I'm likely going to start running Minion jobs on archive discovery+Reader open to preemptively create thumbnails for every page, so this endpoint should be fast enough.
no_fallback allows you to disable the current behavior where a placeholder "No thumbnail" image is returned if your thumb isn't ready, giving you instead a proper error or minion job status.
Should this still return an image if the thumb is ready? There are no other endpoints that serve thumbs so you'd have to re-call the URL without no_fallback which feels a bit dumb, but having an endpoint that can give JSON or image data feels a bit schizophrenic
PUT/api/archives/:id/thumbnail?path=xxx allows you to specify a given thumbnail to be the registered cover.
This option would allow users to fix the few edge cases where the server doesn't detect the proper cover image in the archive.
This doesn't necessarily need an API endpoint and could just be glued to the Reader Controller class, but being a good host to third-party clients is important!
The text was updated successfully, but these errors were encountered: