When query the track record of a manga the last read chapter should match my tracker's last read
Actual behavior
If the last read chapter was not change, the server returns the last read chapter in the database, and it does not check if the last read has changed in the tracker. This result on the server being behind the tracker if the last read chapter was update by another app or manually at the tracker's website.
Other details
By being able to pull the last read chapter in the mutation, clients make sure the last read is updated before query the data(or return it as part of the mutation) .
Expected behavior
When query the track record of a manga the last read chapter should match my tracker's last read
Actual behavior
If the last read chapter was not change, the server returns the last read chapter in the database, and it does not check if the last read has changed in the tracker. This result on the server being behind the tracker if the last read chapter was update by another app or manually at the tracker's website.
Other details
By being able to pull the last read chapter in the mutation, clients make sure the last read is updated before query the data(or return it as part of the mutation) .