b9402b5c47
Context: https://forums.ankiweb.net/t/more-cards-today-question-about-v3/12400/10 Previously, interday learning cards and reviews were gathered at the same time in v3, with the review limit being applied to both of them. The order cards were gathered in would change the ratio of gathered learning cards and reviews, but as they were displayed together in a single count, a changing ratio was not apparent, and no special handling was required by the deck tree code. Showing interday learning cards in the learning count, while still applying a review limit to them, makes things more complicated, as a changing ratio will result in different counts. The deck tree code is not able to know which order cards will appear in, so without changes, we would have had a situation where the deck list may show different counts to those seen when clicking on a deck. One way to solve this would have been to introduce a separate limit for interday learning cards. But this would have meant users needed to juggle two different limits, instead of having a single one that controls total number of (non-intraday) cards shown. Instead, the scheduler now fetches interday cards prior to reviews - the rationale for that order is that learning cards tend to be more fragile/urgent than reviews. The option to show learning cards before/after/mixed with reviews still exists, but it applies only after cards have been capped to the daily limit. To ensure the deck tree code matches the counts the scheduler gives, it too applies limits to interday learning cards first, and reviews afterwards. |
||
|---|---|---|
| .. | ||
| .cargo | ||
| build | ||
| cargo | ||
| i18n | ||
| src | ||
| templates | ||
| tests | ||
| .gitignore | ||
| BUILD.bazel | ||
| Cargo.toml | ||
| empty.rs | ||
| README.md | ||
| rustfmt.bzl | ||
| rustfmt.toml | ||
Anki's Rust code.
backend.proto stores the interfaces used to communicate backend messages between Rust, Python and TypeScript.