Delete User Data extension to allow targeting documents for a given field value
See original GitHub issueExtension name
This feature request is for extension: delete-user-data
What feature would you like to see?
Ability to target documents that match the user ID as one of the fields in Firestore.
One example would be a collection of articles
and each article stores the author’s UID in the authorUID
field. When the user decides to delete their account, all articles the user is the author of should be deleted.
How would you use it?
I’d use this feature to remove all user associated data in Firestore applications.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:6
- Comments:12 (3 by maintainers)
Top Results From Across the Web
Using the Delete User Data extension - Firebase - Google
The Delete User Data extension ( delete-user-data ) lets you delete a user's data when the user is deleted from your Firebase project....
Read more >Delete a Marketing Cloud Data Extension - Salesforce Help
Delete a Marketing Cloud Data Extension · Click Subscribers. · Click Data Extensions. · Select the checkbox next to the name or names...
Read more >Content Management API | Contentful
To delete fields you no longer need, first, omit the field you're targeting for deletion and activate the content type. This step is...
Read more >chrome.storage - Chrome Developers
The Storage API provides an extension-specific way to persist user data and ... sensitive data, consider using the session storage area to hold...
Read more >Appian Administration Console
Allow News Entry Deletion - Allow users to delete news entries and social tasks ... Only allow files with the specified extensions -...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
https://gist.github.com/TylerAHolden/10d0ee986a8a1f743fa09154118b177b
I forgot I also added the ability to delete storage paths based on a field from the userData. In other words, you can pass {DEFAULT}/{userData.avatar} into the storage path variable and it will first get collection(‘users’).doc(UID).get() and then get the avatar field and delete that file from the storage bucket. It’s a pretty hasty implementation but it works!
Hey @bhr, thanks for the feedback. This sounds like a potential feature request candidate.