microsoft / microsoft/azurechat
DeletedAt to replace IsDeleted?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.4k
- Forks
- 1.3k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 1
Description
Hi,
To be able to have good GDPR compliant setup we would like to wipe our users' deleted threads and messages after say 14 days (but possibly keep them around soft-deleted for compliance, security, debugging etc). Currently there is no way of doing that since there is no way to know when a certain thread or message was deleted.
If we were to submit a pull request replacing isDeleted with deletedAt throughout the code, deletedAt having a value if the entity is deleted, or null otherwise, would this be an agreeable solution?
Thank you for your input
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the uses of isDeleted across the TypeScript codebase and review how thread and message deletion currently works. Done would require an agreed retention design and a defined implementation plan for recording deletion times and later purging data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100