Random fixes #2729
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#2729
Loading…
Reference in a new issue
No description provided.
Delete branch "fixes"
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?
In before "there should be a User type"
Will be added...
sometime
@ -88,1 +108,4 @@
});
}
const hidePlayer = !isPlaying || !uri || (!inline && (!floatingPlayerEnabled || !isStreamable));
@tzarebczan brought up that we might not want to do play time (or keep play time separate) for non-streamable content.
@ -99,2 +99,4 @@
rewardEligibleEvent: () => {
sendGaEvent('Engagement', 'Reward-Eligible');
},
};
Making a
sendReactGAEvent
or equivalent function would eliminate these repeated if checks and could also help ensure the checks are not accidentally left out in the future.=== undefined
? or just!previousUserId
?same question for below
undefined
checks@ -88,0 +103,4 @@
const newX = x + ui.deltaX;
const newY = y + ui.deltaY;
setPosition({
x: newX,
😂
@ -88,1 +108,4 @@
});
}
const hidePlayer = !isPlaying || !uri || (!inline && (!floatingPlayerEnabled || !isStreamable));
I'm not particularly concerned about this, I think it can be cleaned up in internal analytics.
@ -7,3 +8,3 @@
closeModal: () => dispatch(doHideModal()),
upload: buffer => dispatch(doUploadThumbnail(null, buffer)),
upload: buffer => dispatch(doUploadThumbnail(null, buffer, null, fs)),
showToast: options => dispatch(doToast(options)),
should these 3rd and 4th params be re-ordered? (meh)
@ -7,3 +8,3 @@
closeModal: () => dispatch(doHideModal()),
upload: path => dispatch(doUploadThumbnail(path)),
upload: path => dispatch(doUploadThumbnail(path, null, null, fs)),
updatePublishForm: value => dispatch(doUpdatePublishForm(value)),
same question as above, if
fs
is regularly provided but other params are not, consider moving fs up in param orderwhen does JS get named parameters?!
could be:
if (!claimIsMine) { logView() }
@ -95,2 +95,4 @@
}
// Quick fix because this is a pain
// There is something weird with wrapping buttons. Some places we want to wrap and others we want to ellips
Good job noting why the rules are being broken so a future dev and/or future you can understand
@ -99,2 +99,4 @@
}
img,
a {
Confident in no consequences to this rule being so universal?
I guess this one specifically could be just be
!previousUserId
but the other ones need to check that they weren'tundefined
so the event isn't fired from the initial user fetch@ -7,3 +8,3 @@
closeModal: () => dispatch(doHideModal()),
upload: buffer => dispatch(doUploadThumbnail(null, buffer)),
upload: buffer => dispatch(doUploadThumbnail(null, buffer, null, fs)),
showToast: options => dispatch(doToast(options)),
The third param is the android equivalent of
fs
@ -99,2 +99,4 @@
}
img,
a {
97% confidence
@ -99,2 +99,4 @@
rewardEligibleEvent: () => {
sendGaEvent('Engagement', 'Reward-Eligible');
},
};
Yeah I've been meaning to do this, just did and it's way nicer now.