Release blockers #1469
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#1469
Loading…
Reference in a new issue
No description provided.
Delete branch "release-blockers"
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?
https://github.com/lbryio/lbry-app/issues/1419
https://github.com/lbryio/lbry-app/issues/1257
https://github.com/lbryio/lbry-app/issues/1264
https://github.com/lbryio/lbry-app/issues/1406
https://github.com/lbryio/lbry-app/issues/1404
https://github.com/lbryio/lbry-app/issues/1478
@seanyesmunt were you still working through this or should we add Jeremy as a reviewer?
Still working on this
On Mon, May 14, 2018, 9:51 AM Thomas Zarebczan notifications@github.com
wrote:
@ -38,2 +38,3 @@
"import/prefer-default-export": 0
"import/prefer-default-export": 0,
"no-return-assign": 0
}
I think we can get rid of this since it is a common patter to return assignments for react refs
LGTM and you can merge at your convenience. One small comment for you to read.