LBRYCommunity/lbry-react-native
1
0
Fork 0
Code Issues Pull requests 12 Projects Releases Packages Wiki Activity

unified display of channel results #108

Merged
akinwale merged 5 commits from channel-results into master 2020-01-09 17:19:31 +01:00
Conversation 0 Commits 5 Files changed 11 +204 -92
akinwale commented 2020-01-08 00:45:54 +01:00 (Migrated from github.com)
Copy link
No description provided.
neb-b (Migrated from github.com) reviewed 2020-01-08 00:45:54 +01:00
kauffj (Migrated from github.com) requested changes 2020-01-09 16:12:16 +01:00
src/component/fileResultItem/view.js
kauffj (Migrated from github.com) commented 2020-01-09 16:09:34 +01:00
Copy link

Random styling should be deterministic based off some specific feature of the item, so that the random value chosen is consistent across different loads, views, orders, etc.

Random styling should be deterministic based off some specific feature of the item, so that the random value chosen is consistent across different loads, views, orders, etc.
kauffj (Migrated from github.com) commented 2020-01-09 16:10:12 +01:00
Copy link

It may make sense to call this ClaimResultItem now?

It may make sense to call this `ClaimResultItem` now?
src/component/suggestedSubscriptionItem/view.js
kauffj (Migrated from github.com) commented 2020-01-09 16:11:36 +01:00
Copy link

This looks very similar to fileResultItem and should probably be a shared component

This looks very similar to fileResultItem and should probably be a shared component
akinwale (Migrated from github.com) reviewed 2020-01-09 16:57:33 +01:00
src/component/fileResultItem/view.js
akinwale (Migrated from github.com) commented 2020-01-09 16:57:33 +01:00
Copy link

Indeed, it does.

Indeed, it does.
akinwale (Migrated from github.com) reviewed 2020-01-09 17:00:31 +01:00
src/component/fileResultItem/view.js
akinwale (Migrated from github.com) commented 2020-01-09 17:00:31 +01:00
Copy link

For this component, there are certain instances where it's possible to not have its properties set, at which point we can't be deterministic. I suppose I could add some code to check this and base the style on the desired property, if it has been set.

For this component, there are certain instances where it's possible to not have its properties set, at which point we can't be deterministic. I suppose I could add some code to check this and base the style on the desired property, if it has been set.
Sign in to join this conversation.
Reviewers
No reviewers
neb-b
kauffj
Labels
Clear labels   
area: devops

   
area: discovery

   
area: docs

   
area: livestream

   
consider soon

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

  
dependencies

Pull requests that update a dependency file

  
documentation

Improvements or additions to documentation

  
Epic

   
good first issue

Good for newcomers

  
hacktoberfest

Welcome to Hacktoberfest

  
help wanted

Extra attention is needed

  
icebox

Long-term storage

  
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

No labels
area: devops
area: discovery
area: docs
area: livestream
consider soon
dependencies
documentation
Epic
good first issue
hacktoberfest
help wanted
icebox
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
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-react-native#108
No description provided.
Delete branch "channel-results"

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?