Store a PlaylistDelta each time we take a snapshot
#111
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…stSnapshot records because they have foreign keys in PlaylistDelta that would need a 'dependent: :destroy' set up in order to be able to destroy the records; I don't want to put that destroy into production in case I accidentally delete a tracked playlist or snapshot in prod - and the test passes with the clean up anyway so I'm not sure why I had it in the first place. I was probably worried about some kind of test pollution
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Every time a new snapshot is taken, that means there was a diff in the playlist.
So let's store that delta in a
PlaylistDeltamodel so that we can display the playlist history timeline from it instead of recomputing it each time.