-
Notifications
You must be signed in to change notification settings - Fork 6
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
Migrate to latest Conviva types #105
Conversation
src/ts/ContentMetadataBuilder.ts
Outdated
}; | ||
const customContentInfo: CustomContentMetadata = { | ||
[Conviva.Constants.FRAMEWORK_NAME]: this.contentMetadata.framework, | ||
[Conviva.Constants.FRAMEWORK_VERSION]: this.contentMetadata.frameworkVersion, |
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.
These two are not present in ReservedContentMetadata
props, so they should be custom data.
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.
I think it would make sense to deprecate/remove those two options in that case. Customers can set any custom data anyway. What do you think?
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 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.
Code looks good to me. Just one open question about the now-custom framework fields
Related to: https://bitmovin.atlassian.net/browse/TA-2596
./@types/conviva/ConvivaExtension.d.ts
with types that are missing in the core package typests-loader
and TypeScript so that the project compiles fine (I've added some comments in the PR with explanations)This PR is required to finalize #104.