3d0ddc8539
This splits update_card() into separate undoable/non-undoable ops like the change to notes in b4396b94abdeba3347d30025c5c0240d991006c9 It means that actions get a blanket 'Update Card' description - in the future we'll probably want to either add specific actions to the backend, or allow an enum or string to be passed in to describe the op. Other changes: - card.flush() can no longer be used to add new cards. Card creation is only supposed to be done in response to changes in a note's fields, and this functionality was only exposed because the card generation hadn't been migrated to the backend at that point. As far as I'm aware, only Arthur's "copy notes" add-on used this functionality, and that should be an easy fix - when the new note is added, the associated cards will be generated, and they can then be retrieved with note.cards() - tidy ups/PEP8 |
||
|---|---|---|
| .. | ||
| anki | ||
| rsbridge | ||
| tests | ||
| tools | ||
| .gitignore | ||
| .isort.cfg | ||
| .pylintrc | ||
| BUILD.bazel | ||
| mypy.ini | ||
| orjson.bzl | ||
| protobuf.bzl | ||
| README.md | ||
Anki's Python library code is in anki/.
The Rust/Python extension module is in rsbridge/; it references the library defined in ../rslib.