e39fb74e82
* Enable state-dependent custom scheduling data * Next(Card)States -> SchedulingStates The fact that `current` was included in `next` always bothered me, and custom data is part of the card state, so that was a bit confusing too. * Store custom_data in SchedulingState * Make custom_data optional when answering Avoids having to send it 4 extra times to the frontend, and avoids the legacy answerCard() API clobbering the stored data. Co-authored-by: Damien Elmes <gpg@ankiweb.net> |
||
|---|---|---|
| .. | ||
| .cargo | ||
| benches | ||
| build | ||
| cargo | ||
| i18n | ||
| i18n_helpers | ||
| linkchecker | ||
| src | ||
| tests/support | ||
| .gitignore | ||
| bench.sh | ||
| 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.