Older rides are all showing as loop rides. Looks like if the loopride value is null in the database, it's coming back as true from the API.
This affects rides c. May 2021 and earlier, which is when the loopride field was added (see #329). After that date, new rides have an explicit true/false value rather than null. We could migrate the old null values to false, but it would be good for the backend to also not assume true if null.
ionous
commented
6 months ago
Older rides are all showing as loop rides. Looks like if the
loopridevalue isnullin the database, it's coming back astruefrom the API.This affects rides c. May 2021 and earlier, which is when the
loopridefield was added (see #329). After that date, new rides have an explicit true/false value rather than null. We could migrate the old null values to false, but it would be good for the backend to also not assume true if null.