The hangup with reading lists

Add another week to implementation of reading lists, not at all surprising. 😉

Here’s what’s going on for the developers among us and also those who want to peer into the Fog of Development. From my worknotes outline, pardon punctuation and capitalization.

i had written code that subscribes all users to new feeds and unsubs from gone feeds, but i didn’t write code that subscribes a new user to all the feeds. now i’ve written it, and i find there’s another bit that i need that this new code needs, we remember the urls of the feeds in the list in json in the reading list record, but we don’t remember the categories each subscription is in. so when we boot up a new user in a reading list, we don’t know what categories to assign

the solution is to go back to where we read the OPML at the beginning, and save all the atts on each subscription, never know what might be needed, and i don’t want to do this retooling again.

there are several places where we convert the feedUrls json text to a list of urls, because of another historical fix here, some of that is happening in the client, have to do it because i’m only updating feedland.org while doing this development.

this change is designed so as not to require a change to the database schema.

i need a whole session to do this, so i’ll do it first thing tomorrow morning.

i’m pretty confident (ha!) at this point that i’ll be able to proceed to work on the reading list info page, which will tie all the reading list ops together the way the feed info page does for feeds.

comparatively the other work on the list seems easy, but we’ll see when we get there