-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove TrackId from Cue #3016
Remove TrackId from Cue #3016
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for fixing this low-hanging fruit that got overlooked.
Nevertheless please avoid modifying unrelated code.
Sorry, old habits. I am used to cleaning up stuff along the way, mostly worked on personal projects previously :) |
f5179a9
to
b3f7fa1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CI builds are still failing.
2b1cbd7
to
b3f7fa1
Compare
Sorry, I didn't trust them lately as I have seen too many CI failures ^^ And sorry for all the force-pushing, that was somewhat accidental... Should be all fine now. |
You could have noticed the build failures locally by enabling The final changeset is clean and matches the goal. Please avoid changing unrelated code in the future. Thank you for fixing this legacy issue. Sometimes a different viewpoint is needed to spot obvious design flaws. LGTM |
Just a quickie I found while talking with Jan, trying to understand db sync :)
The Cue shouldn't know it's owner, the Track, and it doesn't even need to - voila 🎉
I am kinda wondering whether we need the
unsetId
/resetId method at all, since the Track is about to be deleted anyways when this is called. But I don't know enough about the TrackRecord lifecycle for that.