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: expose PartEndState to the adlib actions (#518) [publish] #518
Conversation
…BlueprintPartInstance
…tEndStateForPart. [publish]
Codecov Report
@@ Coverage Diff @@
## release35 #518 +/- ##
=============================================
+ Coverage 67.82% 67.87% +0.04%
=============================================
Files 251 251
Lines 15096 15146 +50
Branches 3534 3555 +21
=============================================
+ Hits 10239 10280 +41
- Misses 4689 4698 +9
Partials 168 168
Continue to review full report at Codecov.
|
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.
Looks good to me!
⚡ Published prerelease version blueprints-integration@1.35.0-nightly-release35-20210528-140916-813cb03.0 to NPM |
⚡ Published prerelease version server-core-integration@1.35.0-nightly-release35-20210528-140916-813cb03.0 to NPM |
Feature
Adlib actions are unable to access the
PartEndState
of the previous part. This data is owned by the blueprints, and is currently only consumed byonTimelineGenerate
and future calls togetPartEndState
Adlib actions are now able to get access this
PartEndState
directly on anyIBlueprintPartInstance
.getPartEndState
has been modified to have access to the fullIBlueprintPartInstance
too, so that it can use themetaData
or other properties.Status