Reconsider or make clearer behaviour of personal fields for new notes #219
Description
Currently, when one imports a new deck (or (I presume — haven't explicitly tested this) new notes into an existing deck) and sets a field as "personal", then that field is set to empty for the new notes. This is completely logical (personal fields mean that we keep the current value of the field, and since the note is non-existent, the current value is (arguably) the empty string), but possibly also confusing.
I see three-ish options:
- Keep the current behaviour (it's logical, in many cases expected and people may rely on it).
- Change the behaviour so that new imports keep the imported/"upstream" value (and only ignore the field (keep the "personal" value) for reimports).
- Make the explanatory text clearer that for new notes, setting a field to personal will mean that that field will be empty.
- Add an extra toggle that will determine which behaviour (keeping new fields empty or using the "upstream" value as the default) will apply for new fields. Possibly this should be a) "global" (for all fields) or b) per-field. (i.e. either have one extra toggle overall or one extra toggle per-field).
AFAICT both behaviours can make sense depending on circumstances (either the personal fields should never use the upstream values or their value should default to the upstream value, but should then be personalised).
(I'm mainly writing this down for my own future reference.)