Allow CmcdConfiguration.Factory to return null to disable CMCD#2183
Closed
MattiasBuelens wants to merge 2 commits intoandroidx:mainfrom
Closed
Allow CmcdConfiguration.Factory to return null to disable CMCD#2183MattiasBuelens wants to merge 2 commits intoandroidx:mainfrom
MattiasBuelens wants to merge 2 commits intoandroidx:mainfrom
Conversation
Contributor
Author
|
Moving to draft for now, I first need to check our company policy on OSS contributions. I'll try to get things sorted out on my end ASAP. |
Contributor
Author
|
I'll reopen this soon from the DolbyLaboratories fork after internal review. Apologies for the confusion! |
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
We would like to enable or disable CMCD selectively for specific media items. This already works today by simply returning
nullfromCmcdConfiguration.Factory.createCmcdConfiguration(), however this behavior is not specified anywhere.This PR updates the return type to be
@Nullable, so this behavior is properly specified and better supported for Kotlin users.