122d561a20
Ticket: 1189 ## Issue There is a bug in a batched `resolve` that returns jumbled data. Temporarily switch to `claim_search` until that is fixed. ## Notable differences: - `resolve` will tell us directly that a claim has been removed or filtered, so redux will mark the ID as such. `claim_search` simply returns nothing, so we will still end up with an extra `resolve` for these items when the component tries to display it. - The new function currently does not handle Collections (i.e. resolving individual items in the Collection) and Reposts. Given that this is temporarily, I'd like to leave `doClaimSearch` as is, instead of trying to replicate what's in `doResolveUris`. ## Notes: Since we don't care if the resolve fails (and we weren't doing anything in the `catch` anyways), use `finally` instead. |
||
|---|---|---|
| .. | ||
| actions | ||
| middleware | ||
| reducers | ||
| selectors | ||