ankidroid/Anki-Android

[Bug] Actual card type must be respected during copy

Open

#8,188 opened on Mar 13, 2021

View on GitHub
 (13 comments) (0 reactions) (0 assignees)Kotlin (2,789 forks)batch import
BugHelp WantedKeep OpenNeeds Triage

Repository metrics

Stars
 (11,132 stars)
PR merge metrics
 (Avg merge 9d 12h) (93 merged PRs in 30d)

Description

Reproduction Steps
  1. Edit a 'Basic with answer input' type card
  2. Copy this card to a new one
  3. Now edit a Close type card
  4. Copy this card to a new one
Expected Result

Card type is respected, so new card also has Close type

Actual Result

Card type is stuck and the latest copy type from step 2 is used (Basic in this case) So after copying and editing several cards you can find all of them have wrong type I'm sure that in 99.9% of cases user wants to copy both content and type, not just content anki

Debug info

AnkiDroid Version = 2.14.6

Android Version = 10

ACRA UUID = 5ff72660-fb1e-445c-9a4a-cd46e651b63a

Scheduler = std2

Crash Reports Enabled = true

Research

Enter an [x] character to confirm the points below:

  • I have read the support page and am reporting a bug or enhancement request specific to AnkiDroid
  • I have checked the manual and the FAQ and could not find a solution to my issue
  • I have searched for similar existing issues here and on the user forum
  • (Optional) I have confirmed the issue is not resolved in the latest alpha release (instructions)

Contributor guide

Research direction
Investigate the card copy logic in AnkiDroid and trace how the card type is determined during copy. Focus on the code path that handles copying from one card type to another and identify why the type is not being updated correctly.
Tech stack
kotlin
Domain
mobile
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitKotlinAndroid development
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65