mirror of
https://github.com/panatgithub/AnkiHeadingSync.git
synced 2026-07-22 06:51:43 +00:00
中文: 修复 pendingWriteBack 持久化加载,丢弃旧 Semantic QA 状态,并修正发布链接与多级列表问答文案。 English: Preserves pendingWriteBack state loading, drops old Semantic QA state, and fixes release links and QA Group wording.
2.3 KiB
2.3 KiB
Pre-release Remaining Fixes Decisions
Pending writeback validation rules
- Preserve modern
PendingWriteBackStateentries during load only when all required fields are valid. - Required fields:
filePath: non-empty stringblockStartLine: positive integerexpectedFileHash: non-empty stringtargetMarker: non-empty stringrawBlockHash: non-empty stringtargetNoteId: positive integer
markerKindrules:undefinedis valid"card-id"is valid"group-gi"is valid- any other value is invalid and drops the item
targetGroupIdrules:- if absent, keep normal validation result
- if present, it must be a non-empty string
- malformed
targetGroupIddrops the item
Legacy pending dropping rule
- Do not migrate legacy pending entries that only contain legacy identity fields such as
cardIdornoteId. - Any pending entry missing
targetNoteIdis dropped. - Do not synthesize or coerce malformed pending items into the modern shape.
Old Semantic QA state dropping rule
- Current supported loaded card state remains limited to:
basiccloze
- Removed card types such as
semantic-qaare dropped during load. - Unknown removed card types are also dropped during load.
- Dropped cards are not written into
state.cards. - File
noteIdsare rebuilt from the filtered migrated card map so dropped cards cannot leave dangling note IDs behind.
README wording decision
- Replace
managed group noteswith current-product wording centered on multi-level list QA cards/notes. - Keep the README change focused to the active feature description only.
i18n wording decision
- Remove user-facing managed-model narrative from active settings copy.
- Replace old wording such as
QA Group 12,ObsiAnki QA Group 12,Managed note type, andManaged model contractwith current route wording for multi-level list QA notes. - Keep internal model-definition constants unchanged unless a user-facing behavior requires a rename.
Intentional deviations from the plan
- Internal technical constants such as
QA_GROUP_MODEL_NAMEare not renamed in this round because the requested cleanup is limited to active user-facing wording and persistence behavior. - Historical audit docs are left untouched even if they still mention old QA Group 12 or Semantic QA history.