TJ Horner
TJ Horner
Since the URL queue (which gets flushed automatically every 15 minutes) is stored in memory, if the user closes their browser, the queue will be lost and the URLs will...
Right now there's lots of manual binding to config changes in the frontend, which can result in really unmaintainable code. The "Archive Mode" setting is also a special case right...
Right now the UX is kind of bad. Once installed, users are not really sure what to do. So, in order to make installation and setup as easy as possible,...
Ideally, the options provided on the add page should also be present in the extension configuration (e.g. crawl depth and extractor methods). In the future, it would also be nice...
When a user adds a domain to their list of sites, the extension should prompt them if they'd like to retroactively archive pages in their history, and how far back...
As described in the original concept for this extension: >If the extension notices a user browsing a certain domain often, it will ask them if they'd like to archive it...
In addition to exporting history, it would be useful to archive bookmarks in a certain folder or based on other criteria.
When publishing a new version of this extension, these manual steps need to be taken by a human (me!): **Chrome Web Store** - Log into dashboard - Zip extension `dist`...
Right now there are no tests! That is not good. To do: - [ ] Unit tests - [ ] Integration tests - [ ] GitHub Actions CI
Everything is just kind of lazily put together in the frontend right now. The CSS sometimes doesn't make sense, e.g. margin is placed on a child component to make it...