feat: add unsubscribe endpoints and user model changes #90
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #77
Adds a JSON field to the DB with info like which list user unsubscribed from and the time they did.
Currently it has only marketing emails, we might expand later on.
To work on the cloud we need to create a manual migration to add the
unsubscribe_id
:Avoided having the user ID for unsubscribing, as this is a pretty public info, and this means bad actors could un-sub other folks.
Currently non of the emails in the repo contain the
List-Unsubscribe
as all of them are operational and not marketing.Our marketing email should include this header. As soon as this is merged, I will run manually migrations for the cloud DB.
CleanShot.2025-09-12.at.11.20.20.mp4