Avoid floating point precision issues when converting scores
Fixes #10343 Maybe we'll finally migrate off of those legacy models some day... (cherry picked from commit f60782f11fd03b302bb81387f24fd56795f3c6bf)
This commit is contained in:
parent
83d85cdd7c
commit
797c385502
@ -40,7 +40,9 @@ fun DbTrack.toDomainTrack(idRequired: Boolean = true): Track? {
|
||||
lastChapterRead = last_chapter_read.toDouble(),
|
||||
totalChapters = total_chapters.toLong(),
|
||||
status = status.toLong(),
|
||||
score = score.toDouble(),
|
||||
// Jank workaround due to precision issues while converting
|
||||
// See https://github.com/tachiyomiorg/tachiyomi/issues/10343
|
||||
score = score.toString().toDouble(),
|
||||
remoteUrl = tracking_url,
|
||||
startDate = started_reading_date,
|
||||
finishDate = finished_reading_date,
|
||||
|
Loading…
x
Reference in New Issue
Block a user