Recommended changes #7089
No reviewers
Labels
No labels
accessibility
app-parity
area: creator
area: daemon
area: design
area: devops
area: discovery
area: docs
area: installer
area: internal
area: livestream
area: performance
area: proposal
area: reposts
area: rewards
area: search
area: security
area: subscriptions
area: sync
area: ux
area: viewer
area: wallet
BEAMER
channel
comments
community PR
consider soon
core team
css
dependencies
electron
Epic
feature request
first-timers-only
good first issue
hacktoberfest
help wanted
hub-dependent
icebox
Invalid
level: 0
level: 1
level: 2
level: 3
level: 4
merge when green
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
notifications
odysee
on hold
playlists
priority: blocker
priority: high
priority: low
priority: medium
protocol dependent
recsys
redesign
regression
resilience
sdk dependent
Tom's Wishlist
trending
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbry-desktop#7089
Loading…
Reference in a new issue
No description provided.
Delete branch "recommended-changes"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fixes
Issue Number: Closes #6434
Other information
PR Checklist
Toggle...
What kind of change does this PR introduce?
Please check all that apply to this PR using "x":
Pretty clean
Good to test/examine whether there's any reason parseURI could fail - we often wrap it in try-catch.
I know this result is the same as previous, but I think we don't necessarily want nsfw: to be set TRUE in search just because the claim is. @tzarebczan
@ -91,0 +124,4 @@
});
// Claim to play next: playable and free claims not played before in history
const nextUriToPlay = recommendedContent.filter((nextRecommendedUri) => {
nice
that's correct, respect the mature content setting.
Yeah that makes sense, specially since you can't even see the content it wouldn't make sense to display nsfw on the sidebar... So I did some changes to the search based on the user setting instead of doing a regular search and filtering later, which would cause only a few videos or none to show up instead of all 20, the results are pretty interesting lol:
@ -16,3 +17,4 @@
INCLUDE_FILES: 'file',
INCLUDE_CHANNELS: 'channel',
INCLUDE_FILES_AND_CHANNELS: 'file,channel',
INCLUDE_MATURE: 'nsfw',
this is good - did you use it anywhere?
@ -35,13 +32,14 @@ export const makeSelectIsPlaying = (uri: string) =>
export const makeSelectIsPlayerFloating = (location: UrlLocation) =>
createSelector(selectPrimaryUri, selectPlayingUri, (primaryUri, playingUri) => {
to me hasSource gets confused with the idea of whether a claim has a source as in livestreams.
hasSecondarySource maybe.
@ -16,3 +17,4 @@
INCLUDE_FILES: 'file',
INCLUDE_CHANNELS: 'channel',
INCLUDE_FILES_AND_CHANNELS: 'file,channel',
INCLUDE_MATURE: 'nsfw',
now I did 👍
Approved assuming testing works out :)