Import: a reminder nested under an application loses its source, note and retired date #1081
Labels
No labels
accessibility
authentication
breaking change
bug
documentation
enhancement
interface
internationalisation
observability
performance
security
tier
1
tier
2
tier
3
tier/4
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Postulo/postulo#1081
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Found while landing #331. An account archive writes each reminder with its
uid,source,noteandretired_at(#887), but a reminder nested under an application is restored withoutsource,noteorretired_at: the importer reads only some of its fields there. A top-level reminder restores them all.So, after an archive round trip, a reminder that came from a calendar file:
What to do
core/importer.py, restoresource,noteandretired_atfor nested reminders, exactly as for top-level ones. #331 addedactorthere; follow that line.tests/test_export.py: a reminder under an application, with a source, a note and a retired date, comes back identical.No format change: the archive already carries the fields.