Closed slice closed 1 year ago
Hmm, okay, looks like this is caused by a new kana_vocabulary
subject type. KanjiSchool doesn't seem to know about it.
Oh dear, yeah, I got an email about this a while ago so knew it was coming up but completely forgot to address it. Will look into this asap
Thanks for the report! I've just pushed an update with basic support for kana vocabulary. The change was pretty invasive (KanjiSchool was very much built around the three 'radical', 'kanji' and 'vocabulary' primitives) but most things seem to work in basic testing. Please do let me know if you find anything strange with it, or any more crashes/errors.
The database should sort itself out automatically when you next force-reload KanjiSchool (Ctrl+Shift+R, or refresh, wait a minute, then refresh again).
I've also made the sync routine skip unknown subject types, so if WaniKani add any more new subject types in the future, it hopefully won't fail so catastrophically!
@Lemmmy Thanks so much for the quick fix on this! 🙏🏼 I'll keep an eye out for any quirks or bugs.
As of 2023-06-21, KanjiSchool can't seem to sync subjects anymore. This happens when loading the database and when creating one from scratch. I suspect that this has to do with recent subjects added by Tofugu.
I get this error:
I used DevTools to pause on the relevant line (
slugCache[subject.object][subject.data.slug] = subject.id;
), so I could see the contents of thesubject
variable:Hopefully this can be of use.