Closed youyingfeng closed 3 years ago
Might consider creating a new class for this with their own dedicated methods, but honestly this might be unnecessary - there are only three extra methods (get all, add to top, delete with workURL) that I have to expose.
In the same vein, the creation of a to-read list is basically the same as reading history.
roadblock: cannot delete nonexistent entry. look into upsert?
ye upsert is actually the best here - its good behaviour for RList, and compulsory for RHistory
Reading list and history methods are complete as of 7e263c1, can abandon original planned integration of history as there is a need to convert these to workers.
Probably need a fixed-size table, 100 entries or so, inserts should remove existing entries first.