At the moment 95% of all cases are handled correctly.
This is a list of all the cases where it doesn't (and their cause):
1) When someone start reading a manga from a chapter different from 1 and the source didn't specify a volume throughout the whole series.
=> Now: Chapter gets set correctly and the volume number doesn't change (standard value is 0).
=> Ideally: Chapter gets set correctly and the volume number gets set to 1.
2) When someone reads a new chapter of a new volume and the source set chapter number to 1 but didn't specify a volume number yet.
=> Now: Chapter number gets set to 1 and volume number also gets set to 1.
=> Ideally: Chapter number either gets ser to 1 or previous chapter number +1 (decided on user preference) and the volume number gets set to last defined volume number +1.
3) When someone reads a new chapter of a new volume and the source didn't specify a volume yet.
=> Now: Chapter number gets set correctly and the volume numbers stays the same as the last defined volume number.
=> Ideally: Chapter number gets set correctly and the volume number gets set to the last defined volume number +1.
I believe most of these cases could be fixed with another api call which checks the current chapter and volume number entry on AniList before updating according that. But that would cause for a lot more api calls, which isn't ideal.
Any tips for fixes or aditions to the list of cases which gets handled incorrectly is welcome.
At the moment 95% of all cases are handled correctly.
This is a list of all the cases where it doesn't (and their cause):
1) When someone start reading a manga from a chapter different from 1 and the source didn't specify a volume throughout the whole series. => Now: Chapter gets set correctly and the volume number doesn't change (standard value is 0). => Ideally: Chapter gets set correctly and the volume number gets set to 1.
2) When someone reads a new chapter of a new volume and the source set chapter number to 1 but didn't specify a volume number yet. => Now: Chapter number gets set to 1 and volume number also gets set to 1. => Ideally: Chapter number either gets ser to 1 or previous chapter number +1 (decided on user preference) and the volume number gets set to last defined volume number +1.
3) When someone reads a new chapter of a new volume and the source didn't specify a volume yet. => Now: Chapter number gets set correctly and the volume numbers stays the same as the last defined volume number. => Ideally: Chapter number gets set correctly and the volume number gets set to the last defined volume number +1.
I believe most of these cases could be fixed with another api call which checks the current chapter and volume number entry on AniList before updating according that. But that would cause for a lot more api calls, which isn't ideal.
Any tips for fixes or aditions to the list of cases which gets handled incorrectly is welcome.