That's a good idea, and worth keeping in mind. Pulling just the ids off of a schedule would be an extremely light process, even for one with 10,000 or more terms in it, so it's definitely possible.
Does the "schedule" endpoint (the one that gives you a list of your schedules) really not give you schedule type (kanji/grammar/word/etc.)? Am I missing something? I'd like to extract the IDs and names for kanji schedules only. You can do it for lists, so I expected the same for schedules.
I had this problem, for my app, how i solved it was caching all schedules I had in a database, then for each schedule, I run 1 page of its contents and check if it had a "japanese" field or a "kanji_full", to keep only sentences and words. I guess you could check if it has an "Onyonmi" or "kunyomi" field. I understand this is not as practical as having a selector built in the call though.
I thought about doing that, but decided to ask first, since it felt a bit extreme... I guess I'll either do that or display all schedules. Trying to load the wrong schedule type doesn't really break anything, it's just not the best in terms of UX. Probably more of a me problem, since I have so many.
Wouldn’t it be more useful to be able to query the schedule endpoint by schedule type? That would not only save you from doing the filter on the client, but insulate clients from future changes in schedule classification.
