cache claim search results by query #166

Merged
neb-b merged 8 commits from cache into master 2019-07-31 21:04:15 +02:00
neb-b commented 2019-07-17 20:11:59 +02:00 (Migrated from github.com)

Changes

  • Change claim_search cache to use the exact options that were used for the claim search to create a key, instead of just tags

    • This requires directly passing in the exact options into claimSearch you want to search with
  • also a couple bugs that we fixed before the last desktop release

#### Changes - Change claim_search cache to use the exact options that were used for the claim search to create a key, instead of just tags - This requires directly passing in the exact `options` into `claimSearch` you want to search with - also a couple bugs that we fixed before the last desktop release
akinwale (Migrated from github.com) reviewed 2019-07-17 20:11:59 +02:00
neb-b commented 2019-07-23 17:02:51 +02:00 (Migrated from github.com)

I'm going to bring these changes into #165 since we don't need both

I'm going to bring these changes into #165 since we don't need both
kauffj (Migrated from github.com) requested changes 2019-07-24 16:58:18 +02:00
kauffj (Migrated from github.com) left a comment

The missing __ is the only necessary comment

The missing `__` is the only necessary comment
kauffj (Migrated from github.com) commented 2019-07-24 16:57:54 +02:00

Missing __

Missing `__`
@ -46,10 +45,9 @@ const defaultState = {
fetchingMyChannels: false,
abandoningById: {},
pendingById: {},
kauffj (Migrated from github.com) commented 2019-07-24 16:55:30 +02:00

what triggers invalidation of this cache? what is the behavior if there are weeks or months old results in here?

what triggers invalidation of this cache? what is the behavior if there are weeks or months old results in here?
kauffj (Migrated from github.com) commented 2019-07-24 16:54:24 +02:00

I'm mildly confused by why this is necessary, but not a blocking comment.

I'm mildly confused by why this is necessary, but not a blocking comment.
kauffj commented 2019-07-24 17:04:43 +02:00 (Migrated from github.com)

Discussions on standup have led me to believe this needs to be thought out more.

Discussions on standup have led me to believe this needs to be thought out more.
neb-b (Migrated from github.com) reviewed 2019-07-30 17:40:38 +02:00
neb-b (Migrated from github.com) commented 2019-07-30 17:40:37 +02:00

It fixed... something. I believe selecting vanity urls

It fixed... something. I believe selecting vanity urls
kauffj (Migrated from github.com) requested changes 2019-07-30 17:54:57 +02:00
kauffj (Migrated from github.com) commented 2019-07-30 17:53:50 +02:00

this means that if thumbnail.url is '' or null, we return undefined

this seems wrong

undefined seems okay if thumbnail.url is undefined itself (i.e. thumbnail is null, not an object, or does not have the url property set)

this means that if `thumbnail.url` is `''` or `null`, we return `undefined` this seems wrong `undefined` seems okay if `thumbnail.url` is undefined itself (i.e. `thumbnail` is null, not an object, or does not have the `url` property set)
kauffj (Migrated from github.com) commented 2019-07-30 17:51:52 +02:00

is this actually used?

is this actually used?
neb-b (Migrated from github.com) reviewed 2019-07-30 17:56:31 +02:00
neb-b (Migrated from github.com) commented 2019-07-30 17:56:31 +02:00

No. And I think others here can be removed

No. And I think others here can be removed
neb-b (Migrated from github.com) reviewed 2019-07-30 17:58:47 +02:00
neb-b (Migrated from github.com) commented 2019-07-30 17:58:47 +02:00

So just return "" if it's an empty string? Instead of undefined?

So just return `""` if it's an empty string? Instead of `undefined`?
neb-b (Migrated from github.com) reviewed 2019-07-30 18:04:27 +02:00
neb-b (Migrated from github.com) commented 2019-07-30 18:04:27 +02:00

Yeah, we weren't even exporting this file. Just deleted it.

Yeah, we weren't even exporting this file. Just deleted it.
Sign in to join this conversation.
No reviewers
No milestone
No project
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#166
No description provided.