Alex Komoroske
Alex Komoroske
With #50 we shifted to having a dict of chunks, but also a side-car of keys by sort, which gets a bit wordy. The original reason for Library's chunks being...
Much of the content people will host is their public content, just in a more convenient format. But some of the content will be private (e.g. unpublished notes or drafts)....
In the library format, chunks must have a unique ID. Currently they are an arbitrary string the library author uses, and by convention are things like the `{article_slug}(_{article_chunk_index})?`. When we...
We currently use `Answer the question as truthfully as possible using the provided context, and if the answer is not contained within the text below, say \"I don't know.\"` but...
Currently it's a particularly-shaped data structure that is passed to a number of different functions. That means the structure of the data has to be known by a number of...
We have a few use cases that need an extra place to stash information--mainly for results from Library.query(). for example, we need a way to pass back: - Number of...
Add schemas in a format where VSCode will naturally validate the various json files and help with autocomplete and catching errors. This is done in https://github.com/jkomoros/CASsim
A lot of chunks have an identical `info` (since the info is related to the article they come from, and many articles have multiple chunks). Now that we've done #15,...
https://help.readwise.io/article/121-how-can-i-customize-the-markdown-export