Feature - deletes

[bcodell]

Ideas:

• <activity>_deletions models that contain two columns: activity_id and deleted_at. users register activities in model config and use a post-hook to apply deletes to registered activities
  • preferred future state
  • need to create post-hook to apply deletes
  • need to recompute activity_occurrence and activity_repeated_at
  • need to update activity_id in activity models to use a non-derived id (breaking change)
• treat deletes as an activity and filter out records that correspond to a delete in datasets
  • probably the current recommended path
  • a more seamless experience would allow for post-query filtering (akin to supporting filters on different activity conditions)

Open questions:

• how to handle edge cases where a record is deleted, then un-deleted?
• should the record be hard deleted from the activity or should a deleted_at field be added?
• when to recompute activity_occurrence and activity_repeated_at - in deletion model post-hook or activity model post-hook?