-
Notifications
You must be signed in to change notification settings - Fork 54
feat: replace wasActive in onRundownActivate with context
#1514
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
feat: replace wasActive in onRundownActivate with context
#1514
Conversation
…rentState in RundownActivationContext. Also changed the algorithm in handleResetRundownPlaylist, so that activateRundownPlaylist always runs This is to provide better context for blueprints, so that they can determine if a RundownPlaylist is being Activated from idle, from Rehersal or a Reset
# Conflicts: # packages/job-worker/src/playout/activePlaylistActions.ts # packages/job-worker/src/playout/activePlaylistJobs.ts # packages/job-worker/src/playout/lib.ts
|
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
Julusian
left a comment
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.
There is a linter and unit test failure, both look to be quick fixes
…tomation#1514) feat: replace `wasActive` in onRundownActivate with previousState¤tState in RundownActivationContext. Also changed the algorithm in handleResetRundownPlaylist, so that activateRundownPlaylist always runs This is to provide better context for blueprints, so that they can determine if a RundownPlaylist is being Activated from idle, from Rehersal or a Reset
About the Contributor
This pull request is posted on behalf of the NRK.
Type of Contribution
This is a: BREAKING CHANGE to the
blueprint-integrationinterface.Current Behavior
Use case:
We (NRK) need to trigger a TSR Action from blueprints at the time a user does a "Reset Rundown".
The problem is that neither one of the blueprints
onRundownActivatenoronRundownDeactivatehooks are called upon a "Reset Rundown".New Behavior
This PR does two things:
activateRundownPlaylist(which does a reset internally)wasActivefromonRundownActivate?: (context: IRundownActivationContext, wasActive: boolean) => Promise<void>(this is a BREAKING CHANGE) and instead addspreviousStateandcurrentStatetoIRundownActivationContextThis allows our blueprints to trigger our TSR Action from
onRundownActivateTesting
Affected areas
This PR affects the blueprints-integration interface.
This PR potentially affects the Reset Rundown method.
Time Frame
We've merged this into our local R52 branch, we would like to get this merged into the in-development release.
Other Information
Status