Skip to content
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: Add getNonDefaultConfiguration #6620

Merged
merged 2 commits into from
May 17, 2024

Conversation

avelad
Copy link
Member

@avelad avelad commented May 16, 2024

No description provided.

@avelad avelad added type: enhancement New feature or request priority: P3 Useful but not urgent labels May 16, 2024
@avelad avelad added this to the v4.9 milestone May 16, 2024
@avelad avelad force-pushed the getNonDefaultConfiguration branch from 71a7ca9 to f2503a2 Compare May 16, 2024 08:30
@shaka-bot
Copy link
Collaborator

shaka-bot commented May 16, 2024

Incremental code coverage: 94.83%

lib/cast/cast_utils.js Outdated Show resolved Hide resolved
lib/player.js Show resolved Hide resolved
@avelad avelad requested a review from theodab May 17, 2024 06:33
@avelad avelad merged commit 907e6ba into shaka-project:main May 17, 2024
16 checks passed
@avelad avelad deleted the getNonDefaultConfiguration branch May 17, 2024 09:04
goog.asserts.assert(this.config_, 'Config must not be null!');

const ret = this.defaultConfig_();
shaka.util.PlayerConfiguration.mergeConfigObjects(
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see why this merge step is necessary. this.config_ should already follow the proper format, right? In fact, you don't even use the result ret here at all.

};

const changes = (object, base) => {
return Object.fromEntries(
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doesn't exist on Tizen, not polyfilled by Babel for testing AFAICT.

@shaka-bot shaka-bot added the status: archived Archived and locked; will not be updated label Jul 16, 2024
@shaka-project shaka-project locked as resolved and limited conversation to collaborators Jul 16, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
priority: P3 Useful but not urgent status: archived Archived and locked; will not be updated type: enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants