LBRYCommunity/lbry-redux
1
0
Fork 0
Code Issues 5 Pull requests 6 Packages Projects Releases Wiki Activity

track reflecting files #310

Merged
jessopb merged 1 commit from feat-trackReflectingFiles into master 2020-05-08 21:07:59 +02:00
Conversation 0 Commits 1 Files changed 10 +289 -9
jessopb commented 2020-05-07 14:25:11 +02:00 (Migrated from github.com)
Copy link
No description provided.
neb-b (Migrated from github.com) requested changes 2020-05-07 17:25:27 +02:00
src/redux/actions/publish.js
neb-b (Migrated from github.com) commented 2020-05-07 17:11:55 +02:00
Copy link

comment

comment
neb-b (Migrated from github.com) commented 2020-05-07 17:17:29 +02:00
Copy link

I think you want const { checkingReflector } = state.publish?

I think you want `const { checkingReflector } = state.publish`?
src/redux/reducers/claims.js
neb-b (Migrated from github.com) commented 2020-05-07 17:20:49 +02:00
Copy link

This should be typed instead of any

This should be typed instead of `any`
src/redux/reducers/claims.js
neb-b (Migrated from github.com) commented 2020-05-07 17:21:18 +02:00
Copy link

extra comment

extra comment
neb-b (Migrated from github.com) commented 2020-05-07 17:22:12 +02:00
Copy link

these comments aren't needed

these comments aren't needed
src/redux/selectors/claims.js
neb-b (Migrated from github.com) commented 2020-05-07 17:25:17 +02:00
Copy link

You should get the claim with the uri first, then get the claim_id from it.

This could fail if you have two claims like lbry://a#a lbry://b#a

You should get the claim with the uri first, then get the claim_id from it. This could fail if you have two claims like `lbry://a#a` `lbry://b#a`
jessopb (Migrated from github.com) reviewed 2020-05-08 18:56:49 +02:00
src/redux/actions/publish.js
jessopb (Migrated from github.com) commented 2020-05-08 18:56:49 +02:00
Copy link

keeping in claims reducer per discussion

keeping in claims reducer per discussion
neb-b (Migrated from github.com) approved these changes 2020-05-08 20:22:03 +02:00
Sign in to join this conversation.
Reviewers
No reviewers
neb-b
Labels
Clear labels   
area: devops

   
area: discovery

   
area: docs

   
area: livestream

   
area: proposal

Work is part of a proposal

  
consider soon

Discuss this issue at the next planning meeting, then remove this label

  
dependencies

Pull requests that update a dependency file

  
Epic

   
good first issue

Good for newcomers

  
hacktoberfest

Welcome to Hacktoberfest

  
help wanted

Extra attention is needed

  
icebox

Long-term storage

  
Invalid

   
level: 1

No knowledge of the existing code required

  
level: 2

Some knowledge of the existing code is recommended

  
level: 3

Significant knowledge of the existing code is recommended

  
level: 4

Intimate knowledge of the existing code is recommended

  
needs: exploration

Solution unclear, needs research

  
needs: grooming

Issue needs to be groomed before work can start

  
needs: priority

Priority level needs to be defined

  
needs: repro

Issue needs step-by-step instructions on how to reproduce in latest code

  
needs: tech design

Needs technical design signoff before implementation can begin

  
on hold

Temporarily paused

  
priority: blocker

Issue is blocking release, do ASAP

  
priority: high

Work needs to be moved into sprint ASAP

  
priority: low

Work should be done but can stay in the backlog for now

  
priority: medium

Work needs to be done within 2-3 sprints

  
resilience

   
Tom's Wishlist

   
type: bug

Existing functionality is wrong or broken

  
type: discussion

A conversation. No specific changes requested

  
type: improvement

Existing (or partially existing) functionality needs to be changed

  
type: new feature

New functionality that does not exist yet

  
type: refactor

Minimal user-visible changes, but significant internal work

  
type: task

Either work that's not related to the code, or a small chore that does not fit into other categories

  
type: testing

Solution needs additional user testing

  
unplanned

Work that was not planned into the spirnt, took priority over planned work

No labels
area: devops
area: discovery
area: docs
area: livestream
area: proposal
consider soon
dependencies
Epic
good first issue
hacktoberfest
help wanted
icebox
Invalid
level: 1
level: 2
level: 3
level: 4
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
on hold
priority: blocker
priority: high
priority: low
priority: medium
resilience
Tom's Wishlist
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbry-redux#310
No description provided.
Delete branch "feat-trackReflectingFiles"

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?