-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create a new kind of revlog entry for reschedule cards on change #3508
Create a new kind of revlog entry for reschedule cards on change #3508
Conversation
for e in group.into_iter() { | ||
if e.button_chosen >= 1 { | ||
last_reviewed_at = Some(e.id.as_secs()); | ||
} | ||
last_revlog_is_manual = e.review_kind == RevlogReviewKind::Manual; | ||
last_revlog_is_rescheduled = e.review_kind == RevlogReviewKind::Rescheduled; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What about older cards that were rated in previous Anki versions. Should we be accepting either manual or rescheduled here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My concern is the user may feel confused if they set due date for a card and reschedule all cards, they will only see the first revlog entry generated by set due date
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This only affects card rescheduling when saving deck options, yes? Won't an upgrading user with previous set due date use see quite different results when rescheduling now, compared to what they were getting previously? Is that intentional?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change aimed at reducing the collection bloat caused by a user experimenting with reschedule multiple times in a short period. But it didn't distinguish "Reschedule cards on change" and "Set Due Date". I think it's a problem, so my PR fix it intentionally.
close #3357