Skip to content

Conversation

@0x5066
Copy link
Contributor

@0x5066 0x5066 commented Nov 29, 2025

The information the media controls gives me is limited, so this implementation is the best I got

The information the media controls gives me is limited, so this implementation is the best I got
@netlify
Copy link

netlify bot commented Nov 29, 2025

Deploy Preview for tourmaline-kringle-c98715 canceled.

Name Link
🔨 Latest commit e50f1b3
🔍 Latest deploy log https://app.netlify.com/projects/tourmaline-kringle-c98715/deploys/692a436c89ee03000844e8df

mediaStatus === MEDIA_STATUS.PLAYING &&
!(kbps != null &&
khz != null &&
kbps.trim() !== "0");
Copy link
Owner

Choose a reason for hiding this comment

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

Maybe this whole expression could become a new selector getIsWorking? That way we would get memoization.

This kbps.trim() !== "0" string comparison seems sus especially given that we do a padded string if kbps is falsy. Are you sure it's "0" and not "00"? Either way, would be much cleaner if we could check this before we transform it into a string.

Very awkward to do "convert nullish/missing into a specific default string" followed by "check for this specific default string to detect if it's nullish/missing.

Better to go up to the source.

@captbaritone
Copy link
Owner

GitHub CI is pointing out legit lint errors here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants