2018-03-26 23:32:43 +02:00
|
|
|
// @flow
|
2021-12-05 04:20:24 +01:00
|
|
|
import { DOMAIN, ENABLE_NO_SOURCE_CLAIMS } from 'config';
|
2020-01-02 21:36:03 +01:00
|
|
|
import * as ICONS from 'constants/icons';
|
2021-04-13 22:47:51 +02:00
|
|
|
import * as PAGES from 'constants/pages';
|
2021-07-23 22:32:19 +02:00
|
|
|
import * as CS from 'constants/claim_search';
|
2020-02-26 20:14:10 +01:00
|
|
|
import React, { useRef } from 'react';
|
2018-03-26 23:32:43 +02:00
|
|
|
import Page from 'component/page';
|
2020-02-26 20:14:10 +01:00
|
|
|
import ClaimListDiscover from 'component/claimListDiscover';
|
|
|
|
import Button from 'component/button';
|
|
|
|
import useHover from 'effects/use-hover';
|
2021-10-19 01:37:58 +02:00
|
|
|
import { useIsMobile } from 'effects/use-screensize';
|
2020-02-26 20:14:10 +01:00
|
|
|
import analytics from 'analytics';
|
|
|
|
import HiddenNsfw from 'component/common/hidden-nsfw';
|
2020-01-02 21:36:03 +01:00
|
|
|
import Icon from 'component/common/icon';
|
2020-11-17 01:04:29 +01:00
|
|
|
import LbcSymbol from 'component/common/lbc-symbol';
|
|
|
|
import I18nMessage from 'component/i18nMessage';
|
Livestream category improvements (#7115)
* ❌ Remove old method of displaying active livestreams
Completely remove it for now to make the commit deltas clearer.
We'll replace it with the new method at the end.
* Fetch and store active-livestream info in redux
* Tiles can now query active-livestream state from redux instead of getting from parent.
* ⏪ ClaimTilesDiscover: revert and cleanup
## Simplify
- Simplify to just `uris` instead of having multiple arrays (`uris`, `modifiedUris`, `prevUris`)
- The `prevUris` is for CLS prevention. With this removal, the CLS issue is back, but we'll handle it differently later.
- Temporarily disable the view-count fetching. Code is left there so that I don't forget.
## Fix
- `shouldPerformSearch` was never true when `prefixUris` is present. Corrected the logic.
- Aside: prefix and pin is so similar in function. Hm ....
* ClaimTilesDiscover: factor out options
## Change
Move the `option` code outside and passed in as a pre-calculated prop.
## Reason
To skip rendering while waiting for `claim_search`, we need to add `React.memo(areEqual)`. However, the flag that determines if we are fetching `claim_search` (fetchingClaimSearchByQuery[]) depends on the derived options as the key.
Instead of calculating `options` twice, we moved it to the props so both sides can use it.
It also makes the component a bit more readable.
The downside is that the prop-passing might not be clear.
* ClaimTilesDiscover: reduce ~17 renders at startup to just 2.
* ClaimTilesDiscover: fill with placeholder while waiting for claim_search
## Issue
Livestream claims are fetched seperately, so they might already exists. While claim_search is running, the list only consists of livestreams (collapsed).
## Fix
Fill up the space with placeholders to prevent layout shift.
* Add 'useFetchViewCount' to handle fetching from lists
This effect also stashes fetched uris, so that we won't re-fetch the same uris during the same instance (e.g. during infinite scroll).
* ⏪ ClaimListDiscover: revert and cleanup
## Revert
- Removed the 'finalUris' stuff that was meant to "pause" visual changes when fetching. I think it'll be cleaner to use React.memo to achieve that.
## Alterations
- Added `renderUri` to make it clear which array that this component will render.
- Re-do the way we fetch view counts now that 'finalUris' is gone. Not the best method, but at least correct for now.
* ClaimListDiscover: add prefixUris, similar to ClaimTilesDiscover
This will be initially used to append livestreams at the top.
* ✅ Re-enable active livestream tiles using the new method
* doFetchActiveLivestreams: add interval check
- Added a default minimum of 5 minutes between fetches. Clients can bypass this through `forceFetch` if needed.
* doFetchActiveLivestreams: add option check
We'll need to support different 'orderBy', so adding an "options check" when determining if we just made the same fetch.
* WildWest: limit livestream tiles + add ability to show more
Most likely this behavior will change in the future, so we'll leave `ClaimListDiscover` untouched and handle the logic at the page level.
This solution uses 2 `ClaimListDiscover` -- if the reduced livestream list is visible, it handles the header; else the normal list handles the header.
* Use better tile-count on larger screens.
Used the same method as how the homepage does it.
2021-09-24 16:26:21 +02:00
|
|
|
|
2021-10-19 01:37:58 +02:00
|
|
|
const LIMIT_CLAIMS_PER_CHANNEL = 3;
|
2019-06-28 09:33:07 +02:00
|
|
|
|
2020-02-26 20:14:10 +01:00
|
|
|
type Props = {
|
|
|
|
location: { search: string },
|
|
|
|
followedTags: Array<Tag>,
|
2020-03-31 22:30:56 +02:00
|
|
|
repostedUri: string,
|
|
|
|
repostedClaim: ?GenericClaim,
|
2021-04-13 22:47:51 +02:00
|
|
|
doToggleTagFollowDesktop: (string) => void,
|
|
|
|
doResolveUri: (string) => void,
|
2020-03-26 22:47:07 +01:00
|
|
|
isAuthenticated: boolean,
|
2020-11-10 17:07:00 +01:00
|
|
|
dynamicRouteProps: RowDataItem,
|
2020-08-21 17:49:13 +02:00
|
|
|
tileLayout: boolean,
|
2020-02-26 20:14:10 +01:00
|
|
|
};
|
|
|
|
|
2020-03-24 17:31:23 +01:00
|
|
|
function DiscoverPage(props: Props) {
|
2020-02-26 20:14:10 +01:00
|
|
|
const {
|
|
|
|
location: { search },
|
|
|
|
followedTags,
|
2020-03-31 22:30:56 +02:00
|
|
|
repostedClaim,
|
|
|
|
repostedUri,
|
2020-03-10 00:46:37 +01:00
|
|
|
doToggleTagFollowDesktop,
|
2020-03-31 22:30:56 +02:00
|
|
|
doResolveUri,
|
2020-08-21 17:49:13 +02:00
|
|
|
tileLayout,
|
2020-11-10 17:07:00 +01:00
|
|
|
dynamicRouteProps,
|
2020-02-26 20:14:10 +01:00
|
|
|
} = props;
|
|
|
|
const buttonRef = useRef();
|
|
|
|
const isHovering = useHover(buttonRef);
|
2020-05-21 17:38:28 +02:00
|
|
|
const isMobile = useIsMobile();
|
2020-02-26 20:14:10 +01:00
|
|
|
|
|
|
|
const urlParams = new URLSearchParams(search);
|
|
|
|
const claimType = urlParams.get('claim_type');
|
2020-03-12 02:43:52 +01:00
|
|
|
const tagsQuery = urlParams.get('t') || null;
|
|
|
|
const tags = tagsQuery ? tagsQuery.split(',') : null;
|
2020-03-31 22:30:56 +02:00
|
|
|
const repostedClaimIsResolved = repostedUri && repostedClaim;
|
2020-03-19 17:54:37 +01:00
|
|
|
|
2021-10-19 01:37:58 +02:00
|
|
|
const discoverIcon = ICONS.DISCOVER;
|
|
|
|
const discoverLabel = __('All Content');
|
2020-02-26 20:14:10 +01:00
|
|
|
// Eventually allow more than one tag on this page
|
|
|
|
// Restricting to one to make follow/unfollow simpler
|
2020-03-12 02:43:52 +01:00
|
|
|
const tag = (tags && tags[0]) || null;
|
Livestream category improvements (#7115)
* ❌ Remove old method of displaying active livestreams
Completely remove it for now to make the commit deltas clearer.
We'll replace it with the new method at the end.
* Fetch and store active-livestream info in redux
* Tiles can now query active-livestream state from redux instead of getting from parent.
* ⏪ ClaimTilesDiscover: revert and cleanup
## Simplify
- Simplify to just `uris` instead of having multiple arrays (`uris`, `modifiedUris`, `prevUris`)
- The `prevUris` is for CLS prevention. With this removal, the CLS issue is back, but we'll handle it differently later.
- Temporarily disable the view-count fetching. Code is left there so that I don't forget.
## Fix
- `shouldPerformSearch` was never true when `prefixUris` is present. Corrected the logic.
- Aside: prefix and pin is so similar in function. Hm ....
* ClaimTilesDiscover: factor out options
## Change
Move the `option` code outside and passed in as a pre-calculated prop.
## Reason
To skip rendering while waiting for `claim_search`, we need to add `React.memo(areEqual)`. However, the flag that determines if we are fetching `claim_search` (fetchingClaimSearchByQuery[]) depends on the derived options as the key.
Instead of calculating `options` twice, we moved it to the props so both sides can use it.
It also makes the component a bit more readable.
The downside is that the prop-passing might not be clear.
* ClaimTilesDiscover: reduce ~17 renders at startup to just 2.
* ClaimTilesDiscover: fill with placeholder while waiting for claim_search
## Issue
Livestream claims are fetched seperately, so they might already exists. While claim_search is running, the list only consists of livestreams (collapsed).
## Fix
Fill up the space with placeholders to prevent layout shift.
* Add 'useFetchViewCount' to handle fetching from lists
This effect also stashes fetched uris, so that we won't re-fetch the same uris during the same instance (e.g. during infinite scroll).
* ⏪ ClaimListDiscover: revert and cleanup
## Revert
- Removed the 'finalUris' stuff that was meant to "pause" visual changes when fetching. I think it'll be cleaner to use React.memo to achieve that.
## Alterations
- Added `renderUri` to make it clear which array that this component will render.
- Re-do the way we fetch view counts now that 'finalUris' is gone. Not the best method, but at least correct for now.
* ClaimListDiscover: add prefixUris, similar to ClaimTilesDiscover
This will be initially used to append livestreams at the top.
* ✅ Re-enable active livestream tiles using the new method
* doFetchActiveLivestreams: add interval check
- Added a default minimum of 5 minutes between fetches. Clients can bypass this through `forceFetch` if needed.
* doFetchActiveLivestreams: add option check
We'll need to support different 'orderBy', so adding an "options check" when determining if we just made the same fetch.
* WildWest: limit livestream tiles + add ability to show more
Most likely this behavior will change in the future, so we'll leave `ClaimListDiscover` untouched and handle the logic at the page level.
This solution uses 2 `ClaimListDiscover` -- if the reduced livestream list is visible, it handles the header; else the normal list handles the header.
* Use better tile-count on larger screens.
Used the same method as how the homepage does it.
2021-09-24 16:26:21 +02:00
|
|
|
const channelIds =
|
|
|
|
(dynamicRouteProps && dynamicRouteProps.options && dynamicRouteProps.options.channelIds) || undefined;
|
2020-02-26 20:14:10 +01:00
|
|
|
|
|
|
|
const isFollowing = followedTags.map(({ name }) => name).includes(tag);
|
2020-10-09 09:13:28 +02:00
|
|
|
let label = isFollowing ? __('Following --[button label indicating a channel has been followed]--') : __('Follow');
|
2020-02-26 20:14:10 +01:00
|
|
|
if (isHovering && isFollowing) {
|
|
|
|
label = __('Unfollow');
|
|
|
|
}
|
|
|
|
|
Livestream category improvements (#7115)
* ❌ Remove old method of displaying active livestreams
Completely remove it for now to make the commit deltas clearer.
We'll replace it with the new method at the end.
* Fetch and store active-livestream info in redux
* Tiles can now query active-livestream state from redux instead of getting from parent.
* ⏪ ClaimTilesDiscover: revert and cleanup
## Simplify
- Simplify to just `uris` instead of having multiple arrays (`uris`, `modifiedUris`, `prevUris`)
- The `prevUris` is for CLS prevention. With this removal, the CLS issue is back, but we'll handle it differently later.
- Temporarily disable the view-count fetching. Code is left there so that I don't forget.
## Fix
- `shouldPerformSearch` was never true when `prefixUris` is present. Corrected the logic.
- Aside: prefix and pin is so similar in function. Hm ....
* ClaimTilesDiscover: factor out options
## Change
Move the `option` code outside and passed in as a pre-calculated prop.
## Reason
To skip rendering while waiting for `claim_search`, we need to add `React.memo(areEqual)`. However, the flag that determines if we are fetching `claim_search` (fetchingClaimSearchByQuery[]) depends on the derived options as the key.
Instead of calculating `options` twice, we moved it to the props so both sides can use it.
It also makes the component a bit more readable.
The downside is that the prop-passing might not be clear.
* ClaimTilesDiscover: reduce ~17 renders at startup to just 2.
* ClaimTilesDiscover: fill with placeholder while waiting for claim_search
## Issue
Livestream claims are fetched seperately, so they might already exists. While claim_search is running, the list only consists of livestreams (collapsed).
## Fix
Fill up the space with placeholders to prevent layout shift.
* Add 'useFetchViewCount' to handle fetching from lists
This effect also stashes fetched uris, so that we won't re-fetch the same uris during the same instance (e.g. during infinite scroll).
* ⏪ ClaimListDiscover: revert and cleanup
## Revert
- Removed the 'finalUris' stuff that was meant to "pause" visual changes when fetching. I think it'll be cleaner to use React.memo to achieve that.
## Alterations
- Added `renderUri` to make it clear which array that this component will render.
- Re-do the way we fetch view counts now that 'finalUris' is gone. Not the best method, but at least correct for now.
* ClaimListDiscover: add prefixUris, similar to ClaimTilesDiscover
This will be initially used to append livestreams at the top.
* ✅ Re-enable active livestream tiles using the new method
* doFetchActiveLivestreams: add interval check
- Added a default minimum of 5 minutes between fetches. Clients can bypass this through `forceFetch` if needed.
* doFetchActiveLivestreams: add option check
We'll need to support different 'orderBy', so adding an "options check" when determining if we just made the same fetch.
* WildWest: limit livestream tiles + add ability to show more
Most likely this behavior will change in the future, so we'll leave `ClaimListDiscover` untouched and handle the logic at the page level.
This solution uses 2 `ClaimListDiscover` -- if the reduced livestream list is visible, it handles the header; else the normal list handles the header.
* Use better tile-count on larger screens.
Used the same method as how the homepage does it.
2021-09-24 16:26:21 +02:00
|
|
|
function getElemMeta() {
|
|
|
|
return !dynamicRouteProps ? (
|
2021-12-05 04:20:24 +01:00
|
|
|
<a
|
|
|
|
className="help"
|
|
|
|
href="https://lbry.com/faq/trending"
|
|
|
|
title={__('Learn more about LBRY Credits on %DOMAIN%', { DOMAIN })}
|
|
|
|
>
|
Livestream category improvements (#7115)
* ❌ Remove old method of displaying active livestreams
Completely remove it for now to make the commit deltas clearer.
We'll replace it with the new method at the end.
* Fetch and store active-livestream info in redux
* Tiles can now query active-livestream state from redux instead of getting from parent.
* ⏪ ClaimTilesDiscover: revert and cleanup
## Simplify
- Simplify to just `uris` instead of having multiple arrays (`uris`, `modifiedUris`, `prevUris`)
- The `prevUris` is for CLS prevention. With this removal, the CLS issue is back, but we'll handle it differently later.
- Temporarily disable the view-count fetching. Code is left there so that I don't forget.
## Fix
- `shouldPerformSearch` was never true when `prefixUris` is present. Corrected the logic.
- Aside: prefix and pin is so similar in function. Hm ....
* ClaimTilesDiscover: factor out options
## Change
Move the `option` code outside and passed in as a pre-calculated prop.
## Reason
To skip rendering while waiting for `claim_search`, we need to add `React.memo(areEqual)`. However, the flag that determines if we are fetching `claim_search` (fetchingClaimSearchByQuery[]) depends on the derived options as the key.
Instead of calculating `options` twice, we moved it to the props so both sides can use it.
It also makes the component a bit more readable.
The downside is that the prop-passing might not be clear.
* ClaimTilesDiscover: reduce ~17 renders at startup to just 2.
* ClaimTilesDiscover: fill with placeholder while waiting for claim_search
## Issue
Livestream claims are fetched seperately, so they might already exists. While claim_search is running, the list only consists of livestreams (collapsed).
## Fix
Fill up the space with placeholders to prevent layout shift.
* Add 'useFetchViewCount' to handle fetching from lists
This effect also stashes fetched uris, so that we won't re-fetch the same uris during the same instance (e.g. during infinite scroll).
* ⏪ ClaimListDiscover: revert and cleanup
## Revert
- Removed the 'finalUris' stuff that was meant to "pause" visual changes when fetching. I think it'll be cleaner to use React.memo to achieve that.
## Alterations
- Added `renderUri` to make it clear which array that this component will render.
- Re-do the way we fetch view counts now that 'finalUris' is gone. Not the best method, but at least correct for now.
* ClaimListDiscover: add prefixUris, similar to ClaimTilesDiscover
This will be initially used to append livestreams at the top.
* ✅ Re-enable active livestream tiles using the new method
* doFetchActiveLivestreams: add interval check
- Added a default minimum of 5 minutes between fetches. Clients can bypass this through `forceFetch` if needed.
* doFetchActiveLivestreams: add option check
We'll need to support different 'orderBy', so adding an "options check" when determining if we just made the same fetch.
* WildWest: limit livestream tiles + add ability to show more
Most likely this behavior will change in the future, so we'll leave `ClaimListDiscover` untouched and handle the logic at the page level.
This solution uses 2 `ClaimListDiscover` -- if the reduced livestream list is visible, it handles the header; else the normal list handles the header.
* Use better tile-count on larger screens.
Used the same method as how the homepage does it.
2021-09-24 16:26:21 +02:00
|
|
|
<I18nMessage
|
|
|
|
tokens={{
|
|
|
|
lbc: <LbcSymbol />,
|
|
|
|
}}
|
|
|
|
>
|
|
|
|
Results boosted by %lbc%
|
|
|
|
</I18nMessage>
|
|
|
|
</a>
|
|
|
|
) : (
|
|
|
|
tag && !isMobile && (
|
|
|
|
<Button
|
|
|
|
ref={buttonRef}
|
|
|
|
button="alt"
|
|
|
|
icon={ICONS.SUBSCRIBE}
|
|
|
|
iconColor="red"
|
|
|
|
onClick={handleFollowClick}
|
|
|
|
label={label}
|
|
|
|
/>
|
|
|
|
)
|
|
|
|
);
|
|
|
|
}
|
|
|
|
|
2020-03-31 22:30:56 +02:00
|
|
|
React.useEffect(() => {
|
|
|
|
if (repostedUri && !repostedClaimIsResolved) {
|
|
|
|
doResolveUri(repostedUri);
|
|
|
|
}
|
|
|
|
}, [repostedUri, repostedClaimIsResolved, doResolveUri]);
|
|
|
|
|
2020-02-26 20:14:10 +01:00
|
|
|
function handleFollowClick() {
|
2020-03-12 02:43:52 +01:00
|
|
|
if (tag) {
|
|
|
|
doToggleTagFollowDesktop(tag);
|
2020-02-26 20:14:10 +01:00
|
|
|
|
2020-03-12 02:43:52 +01:00
|
|
|
const nowFollowing = !isFollowing;
|
|
|
|
analytics.tagFollowEvent(tag, nowFollowing, 'tag-page');
|
|
|
|
}
|
2020-02-26 20:14:10 +01:00
|
|
|
}
|
|
|
|
|
2020-03-19 17:54:37 +01:00
|
|
|
let headerLabel;
|
2020-03-31 22:30:56 +02:00
|
|
|
if (repostedClaim) {
|
|
|
|
headerLabel = __('Reposts of %uri%', { uri: repostedUri });
|
2020-03-19 17:54:37 +01:00
|
|
|
} else if (tag) {
|
|
|
|
headerLabel = (
|
|
|
|
<span>
|
|
|
|
<Icon icon={ICONS.TAG} size={10} />
|
2020-04-29 21:10:58 +02:00
|
|
|
{(tag === CS.TAGS_ALL && __('All Content')) || (tag === CS.TAGS_FOLLOWED && __('Followed Tags')) || tag}
|
2021-04-13 22:47:51 +02:00
|
|
|
|
|
|
|
<Button
|
|
|
|
className="claim-search__tags-link"
|
|
|
|
button="link"
|
|
|
|
label={__('Manage Tags')}
|
|
|
|
navigate={`/$/${PAGES.TAGS_FOLLOWING_MANAGE}`}
|
|
|
|
/>
|
2020-03-19 17:54:37 +01:00
|
|
|
</span>
|
|
|
|
);
|
|
|
|
} else {
|
|
|
|
headerLabel = (
|
|
|
|
<span>
|
2021-07-23 22:32:19 +02:00
|
|
|
<Icon icon={(dynamicRouteProps && dynamicRouteProps.icon) || discoverIcon} size={10} />
|
|
|
|
{(dynamicRouteProps && dynamicRouteProps.title) || discoverLabel}
|
2020-03-19 17:54:37 +01:00
|
|
|
</span>
|
|
|
|
);
|
|
|
|
}
|
|
|
|
|
2021-10-19 01:37:58 +02:00
|
|
|
// GET ELEM DATA??
|
2019-06-11 20:10:58 +02:00
|
|
|
return (
|
2020-08-21 17:49:13 +02:00
|
|
|
<Page noFooter fullWidthPage={tileLayout}>
|
2020-01-02 21:36:03 +01:00
|
|
|
<ClaimListDiscover
|
2020-09-17 17:49:53 +02:00
|
|
|
tileLayout={repostedUri ? false : tileLayout}
|
2020-02-29 00:13:49 +01:00
|
|
|
claimType={claimType ? [claimType] : undefined}
|
2021-10-19 01:37:58 +02:00
|
|
|
headerLabel={headerLabel}
|
2020-03-19 17:54:37 +01:00
|
|
|
tags={tags}
|
2020-02-26 20:14:10 +01:00
|
|
|
hiddenNsfwMessage={<HiddenNsfw type="page" />}
|
2020-03-31 22:30:56 +02:00
|
|
|
repostedClaimId={repostedClaim ? repostedClaim.claim_id : null}
|
2021-07-23 22:32:19 +02:00
|
|
|
// Assume wild west page if no dynamicRouteProps
|
|
|
|
// Not a very good solution, but just doing it for now
|
|
|
|
// until we are sure this page will stay around
|
2021-08-01 22:38:00 +02:00
|
|
|
// TODO: find a better way to determine discover / wild west vs other modes release times
|
|
|
|
// for now including && !tags so that
|
Livestream category improvements (#7115)
* ❌ Remove old method of displaying active livestreams
Completely remove it for now to make the commit deltas clearer.
We'll replace it with the new method at the end.
* Fetch and store active-livestream info in redux
* Tiles can now query active-livestream state from redux instead of getting from parent.
* ⏪ ClaimTilesDiscover: revert and cleanup
## Simplify
- Simplify to just `uris` instead of having multiple arrays (`uris`, `modifiedUris`, `prevUris`)
- The `prevUris` is for CLS prevention. With this removal, the CLS issue is back, but we'll handle it differently later.
- Temporarily disable the view-count fetching. Code is left there so that I don't forget.
## Fix
- `shouldPerformSearch` was never true when `prefixUris` is present. Corrected the logic.
- Aside: prefix and pin is so similar in function. Hm ....
* ClaimTilesDiscover: factor out options
## Change
Move the `option` code outside and passed in as a pre-calculated prop.
## Reason
To skip rendering while waiting for `claim_search`, we need to add `React.memo(areEqual)`. However, the flag that determines if we are fetching `claim_search` (fetchingClaimSearchByQuery[]) depends on the derived options as the key.
Instead of calculating `options` twice, we moved it to the props so both sides can use it.
It also makes the component a bit more readable.
The downside is that the prop-passing might not be clear.
* ClaimTilesDiscover: reduce ~17 renders at startup to just 2.
* ClaimTilesDiscover: fill with placeholder while waiting for claim_search
## Issue
Livestream claims are fetched seperately, so they might already exists. While claim_search is running, the list only consists of livestreams (collapsed).
## Fix
Fill up the space with placeholders to prevent layout shift.
* Add 'useFetchViewCount' to handle fetching from lists
This effect also stashes fetched uris, so that we won't re-fetch the same uris during the same instance (e.g. during infinite scroll).
* ⏪ ClaimListDiscover: revert and cleanup
## Revert
- Removed the 'finalUris' stuff that was meant to "pause" visual changes when fetching. I think it'll be cleaner to use React.memo to achieve that.
## Alterations
- Added `renderUri` to make it clear which array that this component will render.
- Re-do the way we fetch view counts now that 'finalUris' is gone. Not the best method, but at least correct for now.
* ClaimListDiscover: add prefixUris, similar to ClaimTilesDiscover
This will be initially used to append livestreams at the top.
* ✅ Re-enable active livestream tiles using the new method
* doFetchActiveLivestreams: add interval check
- Added a default minimum of 5 minutes between fetches. Clients can bypass this through `forceFetch` if needed.
* doFetchActiveLivestreams: add option check
We'll need to support different 'orderBy', so adding an "options check" when determining if we just made the same fetch.
* WildWest: limit livestream tiles + add ability to show more
Most likely this behavior will change in the future, so we'll leave `ClaimListDiscover` untouched and handle the logic at the page level.
This solution uses 2 `ClaimListDiscover` -- if the reduced livestream list is visible, it handles the header; else the normal list handles the header.
* Use better tile-count on larger screens.
Used the same method as how the homepage does it.
2021-09-24 16:26:21 +02:00
|
|
|
channelIds={channelIds}
|
2021-10-19 01:37:58 +02:00
|
|
|
limitClaimsPerChannel={LIMIT_CLAIMS_PER_CHANNEL}
|
|
|
|
meta={getElemMeta()}
|
2021-04-29 11:33:24 +02:00
|
|
|
hasSource
|
2021-12-05 04:20:24 +01:00
|
|
|
showNoSourceClaims={ENABLE_NO_SOURCE_CLAIMS}
|
2020-01-02 21:36:03 +01:00
|
|
|
/>
|
2019-06-11 20:10:58 +02:00
|
|
|
</Page>
|
|
|
|
);
|
2017-05-04 05:44:08 +02:00
|
|
|
}
|
|
|
|
|
2020-03-24 17:31:23 +01:00
|
|
|
export default DiscoverPage;
|