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
Season support
Reason: It's annoying to do the separation of seasons manually, and bugs can easily appear in the implementation of some extensions.
Theoretical implementation: A new property (season_number: Int, default: 0) could be added to the SEpisode model, and the episode list would be grouped according to season and episode number, maybe adding the season number as a prefix or something.
Re-implementation of pagination in episodeList-related functions
Reason: This was removed on this commit, and can help devs when fetching the episode list on sources that uses multiple pages. Currently we need to reinvent the wheel and create similar functions.
Problem: This will surely break some extensions >:(
Expose the Response.parseAs function
Reason: It may be useful for JSON-API oriented extensions.
Automatically generated documentation page
Reason: This will be VERY useful for new and future contributors to aniyomi-extensions.
Theoretical implementation: Maybe KDocs or something can help with that. Explaining better the functions exposed via extensions-lib and by adding usage examples, the documentation will be even clearer and will facilitate future extension development.
The text was updated successfully, but these errors were encountered:
Reason: It's annoying to do the separation of seasons manually, and bugs can easily appear in the implementation of some extensions.
Theoretical implementation: A new property (season_number: Int, default: 0) could be added to the SEpisode model, and the episode list would be grouped according to season and episode number, maybe adding the season number as a prefix or something.
episodeList
-related functionsReason: This was removed on this commit, and can help devs when fetching the episode list on sources that uses multiple pages. Currently we need to reinvent the wheel and create similar functions.
Problem: This will surely break some extensions >:(
Response.parseAs
functionReason: It may be useful for JSON-API oriented extensions.
Reason: This will be VERY useful for new and future contributors to aniyomi-extensions.
Theoretical implementation: Maybe KDocs or something can help with that. Explaining better the functions exposed via extensions-lib and by adding usage examples, the documentation will be even clearer and will facilitate future extension development.
The text was updated successfully, but these errors were encountered: