LBRYCommunity/lbry-desktop

Fork

You've already forked lbry-desktop

Code Issues 596 Pull requests 6 Projects Releases 238 Packages Wiki Activity

Add ability to search through publishes. #7535

Merged

Ruk33 merged 8 commits from 3139-ability-to-search-through-publishes into master

2022-04-15 05:06:00 +02:00

Conversation 2 Commits 8 Files changed 9 +162 -37

Ruk33 commented

2022-04-06 16:54:38 +02:00

(Migrated from github.com)

Copy link

Fixes

Issue Number: https://github.com/lbryio/lbry-desktop/issues/3139

What is the current behavior?

Users can't search through their publishes.

What is the new behavior?

Users can search through their publishes:

Other information

PR Checklist

Toggle...

What kind of change does this PR introduce?

Bugfix
Feature
Code style update (formatting)
Refactoring (no functional changes)
Documentation changes
Other - Please describe:

Please check all that apply to this PR using "x":

I have checked that this PR is not a duplicate of an existing PR (open, closed or merged)
I added a line describing my change to CHANGELOG.md
I have checked that this PR does not introduce a breaking change
This PR introduces breaking changes and I have provided a detailed explanation below

## Fixes Issue Number: https://github.com/lbryio/lbry-desktop/issues/3139  ## What is the current behavior? Users can't search through their publishes. ## What is the new behavior? Users can search through their publishes: ![image](https://user-images.githubusercontent.com/1719111/162003765-7777f533-08c2-4999-ae35-73ee21d32f75.png) ![image](https://user-images.githubusercontent.com/1719111/162003843-cbd0a7d8-0a0a-463f-85aa-53656b902a15.png) ![image](https://user-images.githubusercontent.com/1719111/162003899-81ac4b89-ce39-4a72-9dd7-80f8896abc99.png) ## Other information  ## PR Checklist  <details><summary>Toggle...</summary> What kind of change does this PR introduce? - [ ] Bugfix - [x] Feature - [ ] Code style update (formatting) - [ ] Refactoring (no functional changes) - [ ] Documentation changes - [ ] Other - Please describe: Please check all that apply to this PR using "x": - [x] I have checked that this PR is not a duplicate of an existing PR (open, closed or merged) - [ ] I added a line describing my change to CHANGELOG.md - [x] I have checked that this PR does not introduce a breaking change - [ ] This PR introduces breaking changes and I have provided a detailed explanation below </details>

Ruk33 (Migrated from github.com) reviewed 2022-04-06 17:41:52 +02:00

ui/page/fileListPublished/view.jsx

					
				@ -35,3 +53,4 @@

				  const { search } = location;

				  const params = {};

				  params[PAGE_PARAM] = Number(page);

Ruk33 (Migrated from github.com) commented

2022-04-06 17:41:52 +02:00

Copy link

@jessopb I'm not entirely happy with this but I couldn't think of a better way to work around this issue.

jessopb (Migrated from github.com) reviewed 2022-04-07 15:05:19 +02:00

ui/page/fileListPublished/view.jsx

					
				@ -35,3 +53,4 @@

				  const { search } = location;

				  const params = {};

				  params[PAGE_PARAM] = Number(page);

jessopb (Migrated from github.com) commented

2022-04-07 15:05:19 +02:00

Copy link

Seems to work really well. I don't think you need "disableHistory" - that mostly doesn't exist except if it's passed to <Paginate as a prop, and only on one page.

jessopb commented

2022-04-07 15:05:26 +02:00

(Migrated from github.com)

Copy link

I think this works well. 3 things,

During loading, let's not say "No results".
It would be good to debounce the filtering while typing?
Maybe make Reposts searchable or disabled?

I think this works well. 3 things, 1) During loading, let's not say "No results". 2) It would be good to debounce the filtering while typing? 3) Maybe make Reposts searchable or disabled?

jessopb commented

2022-04-07 17:12:10 +02:00

(Migrated from github.com)

Copy link

I think we should put the search term in the params too, so when you navigate forward, then back again, you have both page and search term.

Ruk33 (Migrated from github.com) reviewed 2022-04-15 02:42:44 +02:00

ui/page/fileListPublished/view.jsx

					
				@ -35,3 +53,4 @@

				  const { search } = location;

				  const params = {};

				  params[PAGE_PARAM] = Number(page);

Ruk33 (Migrated from github.com) commented

2022-04-15 02:42:44 +02:00

Copy link

Updated. Thanks @jessopb for the comment.

Reviewers

No reviewers

Labels

Clear labels

Work is part of a proposal

Beamer is waiting on you!

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

Welcome to Hacktoberfest

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

merge when green

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

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

protocol dependent

recsys

redesign

general redesign not prioritize for anyone release

regression

resilience

sdk dependent

Requires work on lbry-sdk repo

Tom's Wishlist

trending

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

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-desktop#7535

Reference in a new issue

Repository

LBRYCommunity/lbry-desktop

Title

Body

No description provided.

Delete branch "3139-ability-to-search-through-publishes"

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?