2018-07-25 02:50:04 +02:00
|
|
|
// @flow
|
2021-06-22 18:33:18 +02:00
|
|
|
import { SHOW_ADS } from 'config';
|
2018-07-25 02:50:04 +02:00
|
|
|
import React from 'react';
|
2019-06-19 07:05:43 +02:00
|
|
|
import ClaimList from 'component/claimList';
|
2021-04-06 20:59:12 +02:00
|
|
|
import ClaimListDiscover from 'component/claimListDiscover';
|
2020-05-07 20:44:11 +02:00
|
|
|
import Ads from 'web/component/ads';
|
2020-04-29 21:31:11 +02:00
|
|
|
import Card from 'component/common/card';
|
2020-08-25 15:49:19 +02:00
|
|
|
import { useIsMobile, useIsMediumScreen } from 'effects/use-screensize';
|
2021-04-06 20:59:12 +02:00
|
|
|
import Button from 'component/button';
|
2021-04-08 17:21:45 +02:00
|
|
|
import classnames from 'classnames';
|
2021-09-03 00:39:40 +02:00
|
|
|
import RecSys from 'recsys';
|
2021-04-08 17:21:45 +02:00
|
|
|
|
|
|
|
const VIEW_ALL_RELATED = 'view_all_related';
|
|
|
|
const VIEW_MORE_FROM = 'view_more_from';
|
2018-07-25 02:50:04 +02:00
|
|
|
|
|
|
|
type Props = {
|
2018-07-25 06:45:24 +02:00
|
|
|
uri: string,
|
2021-09-03 00:39:40 +02:00
|
|
|
recommendedContentUris: Array<string>,
|
2021-03-19 04:16:05 +01:00
|
|
|
nextRecommendedUri: string,
|
2018-08-27 05:18:57 +02:00
|
|
|
isSearching: boolean,
|
2021-03-19 16:04:12 +01:00
|
|
|
doFetchRecommendedContent: (string, boolean) => void,
|
2020-01-28 23:05:44 +01:00
|
|
|
mature: boolean,
|
2020-03-26 22:47:07 +01:00
|
|
|
isAuthenticated: boolean,
|
2021-04-08 17:21:45 +02:00
|
|
|
claim: ?StreamClaim,
|
Fill in remaining Recsys fields
## Issue
6366 Recsys Evaluation Telemetry
The recommended list from lighthouse is obtained from `makeSelectRecommendedContentForUri`. This list is further tweaked by the GUI (e.g. move autoplay next item to top, remove blocked content, etc.). Recsys wants the final recommendation list and the clicked index (in exact order), so we need pass these info to the videojs recsys plugin somehow. Also, Recsys wants a recommendation list ID as well as the parent (referrer) ID, we so need to track the clicks and navigation.
## General Approach
- It seems easiest to just spew back the final (displayed) list and all the required info to Redux, and the recsys plugin (or anyone else in the future) can grab it.
- Try to touch few files as possible. The dirty work should all reside in `<RecommendedContent>` only.
## Changes
- `ClaimPreview`: add optional parameters to store an ID of the container that it is in (for this case, it is `ClaimList`) as well as the index within the container.
- When clicked, we store the container ID in the navigation history `state` object.
- For general cases, anyone can check this state from `history.location.state` to know which container referred/navigated to the current page. For the recsys use case, we can use this as the `parentUUID`.
- `ClaimList`: just relay `onClick` and set IDs.
- `RecommendedContent`: now handles the uuid generation (for both parent and child) and stores the data in Redux.
2021-07-28 14:07:49 +02:00
|
|
|
doRecommendationUpdate: (claimId: string, urls: Array<string>, id: string, parentId: string) => void,
|
2021-09-03 00:39:40 +02:00
|
|
|
claimId: string,
|
2018-07-25 02:50:04 +02:00
|
|
|
};
|
|
|
|
|
2021-06-28 10:38:48 +02:00
|
|
|
export default React.memo<Props>(function RecommendedContent(props: Props) {
|
2021-03-19 16:04:12 +01:00
|
|
|
const {
|
|
|
|
uri,
|
|
|
|
doFetchRecommendedContent,
|
|
|
|
mature,
|
2021-09-03 00:39:40 +02:00
|
|
|
recommendedContentUris,
|
2021-03-19 16:04:12 +01:00
|
|
|
nextRecommendedUri,
|
|
|
|
isSearching,
|
|
|
|
isAuthenticated,
|
2021-04-08 17:21:45 +02:00
|
|
|
claim,
|
2021-09-03 00:39:40 +02:00
|
|
|
claimId,
|
2021-03-19 16:04:12 +01:00
|
|
|
} = props;
|
2021-04-08 17:21:45 +02:00
|
|
|
const [viewMode, setViewMode] = React.useState(VIEW_ALL_RELATED);
|
Fill in remaining Recsys fields
## Issue
6366 Recsys Evaluation Telemetry
The recommended list from lighthouse is obtained from `makeSelectRecommendedContentForUri`. This list is further tweaked by the GUI (e.g. move autoplay next item to top, remove blocked content, etc.). Recsys wants the final recommendation list and the clicked index (in exact order), so we need pass these info to the videojs recsys plugin somehow. Also, Recsys wants a recommendation list ID as well as the parent (referrer) ID, we so need to track the clicks and navigation.
## General Approach
- It seems easiest to just spew back the final (displayed) list and all the required info to Redux, and the recsys plugin (or anyone else in the future) can grab it.
- Try to touch few files as possible. The dirty work should all reside in `<RecommendedContent>` only.
## Changes
- `ClaimPreview`: add optional parameters to store an ID of the container that it is in (for this case, it is `ClaimList`) as well as the index within the container.
- When clicked, we store the container ID in the navigation history `state` object.
- For general cases, anyone can check this state from `history.location.state` to know which container referred/navigated to the current page. For the recsys use case, we can use this as the `parentUUID`.
- `ClaimList`: just relay `onClick` and set IDs.
- `RecommendedContent`: now handles the uuid generation (for both parent and child) and stores the data in Redux.
2021-07-28 14:07:49 +02:00
|
|
|
const [recommendationUrls, setRecommendationUrls] = React.useState();
|
2021-04-08 17:21:45 +02:00
|
|
|
const signingChannel = claim && claim.signing_channel;
|
|
|
|
const channelName = signingChannel ? signingChannel.name : null;
|
2020-08-25 15:49:19 +02:00
|
|
|
const isMobile = useIsMobile();
|
|
|
|
const isMedium = useIsMediumScreen();
|
2021-09-03 00:39:40 +02:00
|
|
|
const { onRecsLoaded: onRecommendationsLoaded, onClickedRecommended: onRecommendationClicked } = RecSys;
|
Fill in remaining Recsys fields
## Issue
6366 Recsys Evaluation Telemetry
The recommended list from lighthouse is obtained from `makeSelectRecommendedContentForUri`. This list is further tweaked by the GUI (e.g. move autoplay next item to top, remove blocked content, etc.). Recsys wants the final recommendation list and the clicked index (in exact order), so we need pass these info to the videojs recsys plugin somehow. Also, Recsys wants a recommendation list ID as well as the parent (referrer) ID, we so need to track the clicks and navigation.
## General Approach
- It seems easiest to just spew back the final (displayed) list and all the required info to Redux, and the recsys plugin (or anyone else in the future) can grab it.
- Try to touch few files as possible. The dirty work should all reside in `<RecommendedContent>` only.
## Changes
- `ClaimPreview`: add optional parameters to store an ID of the container that it is in (for this case, it is `ClaimList`) as well as the index within the container.
- When clicked, we store the container ID in the navigation history `state` object.
- For general cases, anyone can check this state from `history.location.state` to know which container referred/navigated to the current page. For the recsys use case, we can use this as the `parentUUID`.
- `ClaimList`: just relay `onClick` and set IDs.
- `RecommendedContent`: now handles the uuid generation (for both parent and child) and stores the data in Redux.
2021-07-28 14:07:49 +02:00
|
|
|
React.useEffect(() => {
|
|
|
|
function moveAutoplayNextItemToTop(recommendedContent) {
|
|
|
|
let newList = recommendedContent;
|
|
|
|
if (newList) {
|
|
|
|
const index = newList.indexOf(nextRecommendedUri);
|
|
|
|
if (index > 0) {
|
|
|
|
const a = newList[0];
|
|
|
|
newList[0] = nextRecommendedUri;
|
|
|
|
newList[index] = a;
|
|
|
|
}
|
2021-03-19 04:16:05 +01:00
|
|
|
}
|
Fill in remaining Recsys fields
## Issue
6366 Recsys Evaluation Telemetry
The recommended list from lighthouse is obtained from `makeSelectRecommendedContentForUri`. This list is further tweaked by the GUI (e.g. move autoplay next item to top, remove blocked content, etc.). Recsys wants the final recommendation list and the clicked index (in exact order), so we need pass these info to the videojs recsys plugin somehow. Also, Recsys wants a recommendation list ID as well as the parent (referrer) ID, we so need to track the clicks and navigation.
## General Approach
- It seems easiest to just spew back the final (displayed) list and all the required info to Redux, and the recsys plugin (or anyone else in the future) can grab it.
- Try to touch few files as possible. The dirty work should all reside in `<RecommendedContent>` only.
## Changes
- `ClaimPreview`: add optional parameters to store an ID of the container that it is in (for this case, it is `ClaimList`) as well as the index within the container.
- When clicked, we store the container ID in the navigation history `state` object.
- For general cases, anyone can check this state from `history.location.state` to know which container referred/navigated to the current page. For the recsys use case, we can use this as the `parentUUID`.
- `ClaimList`: just relay `onClick` and set IDs.
- `RecommendedContent`: now handles the uuid generation (for both parent and child) and stores the data in Redux.
2021-07-28 14:07:49 +02:00
|
|
|
return newList;
|
2021-03-19 04:16:05 +01:00
|
|
|
}
|
Fill in remaining Recsys fields
## Issue
6366 Recsys Evaluation Telemetry
The recommended list from lighthouse is obtained from `makeSelectRecommendedContentForUri`. This list is further tweaked by the GUI (e.g. move autoplay next item to top, remove blocked content, etc.). Recsys wants the final recommendation list and the clicked index (in exact order), so we need pass these info to the videojs recsys plugin somehow. Also, Recsys wants a recommendation list ID as well as the parent (referrer) ID, we so need to track the clicks and navigation.
## General Approach
- It seems easiest to just spew back the final (displayed) list and all the required info to Redux, and the recsys plugin (or anyone else in the future) can grab it.
- Try to touch few files as possible. The dirty work should all reside in `<RecommendedContent>` only.
## Changes
- `ClaimPreview`: add optional parameters to store an ID of the container that it is in (for this case, it is `ClaimList`) as well as the index within the container.
- When clicked, we store the container ID in the navigation history `state` object.
- For general cases, anyone can check this state from `history.location.state` to know which container referred/navigated to the current page. For the recsys use case, we can use this as the `parentUUID`.
- `ClaimList`: just relay `onClick` and set IDs.
- `RecommendedContent`: now handles the uuid generation (for both parent and child) and stores the data in Redux.
2021-07-28 14:07:49 +02:00
|
|
|
|
|
|
|
function listEq(prev, next) {
|
|
|
|
if (prev && next) {
|
|
|
|
return prev.length === next.length && prev.every((value, index) => value === next[index]);
|
|
|
|
} else {
|
|
|
|
return prev === next;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2021-09-03 00:39:40 +02:00
|
|
|
const newRecommendationUrls = moveAutoplayNextItemToTop(recommendedContentUris);
|
Fill in remaining Recsys fields
## Issue
6366 Recsys Evaluation Telemetry
The recommended list from lighthouse is obtained from `makeSelectRecommendedContentForUri`. This list is further tweaked by the GUI (e.g. move autoplay next item to top, remove blocked content, etc.). Recsys wants the final recommendation list and the clicked index (in exact order), so we need pass these info to the videojs recsys plugin somehow. Also, Recsys wants a recommendation list ID as well as the parent (referrer) ID, we so need to track the clicks and navigation.
## General Approach
- It seems easiest to just spew back the final (displayed) list and all the required info to Redux, and the recsys plugin (or anyone else in the future) can grab it.
- Try to touch few files as possible. The dirty work should all reside in `<RecommendedContent>` only.
## Changes
- `ClaimPreview`: add optional parameters to store an ID of the container that it is in (for this case, it is `ClaimList`) as well as the index within the container.
- When clicked, we store the container ID in the navigation history `state` object.
- For general cases, anyone can check this state from `history.location.state` to know which container referred/navigated to the current page. For the recsys use case, we can use this as the `parentUUID`.
- `ClaimList`: just relay `onClick` and set IDs.
- `RecommendedContent`: now handles the uuid generation (for both parent and child) and stores the data in Redux.
2021-07-28 14:07:49 +02:00
|
|
|
|
|
|
|
if (claim && !listEq(recommendationUrls, newRecommendationUrls)) {
|
|
|
|
setRecommendationUrls(newRecommendationUrls);
|
|
|
|
}
|
2021-09-03 00:39:40 +02:00
|
|
|
}, [recommendedContentUris, nextRecommendedUri, recommendationUrls, setRecommendationUrls, claim]);
|
2021-03-19 04:16:05 +01:00
|
|
|
|
2020-08-25 15:49:19 +02:00
|
|
|
React.useEffect(() => {
|
2021-03-19 16:04:12 +01:00
|
|
|
doFetchRecommendedContent(uri, mature);
|
|
|
|
}, [uri, mature, doFetchRecommendedContent]);
|
2018-08-09 18:41:14 +02:00
|
|
|
|
2021-09-03 00:39:40 +02:00
|
|
|
React.useEffect(() => {
|
|
|
|
// Right now we only want to record the recs if they actually saw them.
|
|
|
|
if (recommendationUrls && recommendationUrls.length && nextRecommendedUri && viewMode === VIEW_ALL_RELATED) {
|
|
|
|
onRecommendationsLoaded(claimId, recommendationUrls);
|
|
|
|
}
|
|
|
|
}, [recommendationUrls, onRecommendationsLoaded, claimId, nextRecommendedUri, viewMode]);
|
|
|
|
|
|
|
|
function handleRecommendationClicked(e, clickedClaim, index: number) {
|
Fill in remaining Recsys fields
## Issue
6366 Recsys Evaluation Telemetry
The recommended list from lighthouse is obtained from `makeSelectRecommendedContentForUri`. This list is further tweaked by the GUI (e.g. move autoplay next item to top, remove blocked content, etc.). Recsys wants the final recommendation list and the clicked index (in exact order), so we need pass these info to the videojs recsys plugin somehow. Also, Recsys wants a recommendation list ID as well as the parent (referrer) ID, we so need to track the clicks and navigation.
## General Approach
- It seems easiest to just spew back the final (displayed) list and all the required info to Redux, and the recsys plugin (or anyone else in the future) can grab it.
- Try to touch few files as possible. The dirty work should all reside in `<RecommendedContent>` only.
## Changes
- `ClaimPreview`: add optional parameters to store an ID of the container that it is in (for this case, it is `ClaimList`) as well as the index within the container.
- When clicked, we store the container ID in the navigation history `state` object.
- For general cases, anyone can check this state from `history.location.state` to know which container referred/navigated to the current page. For the recsys use case, we can use this as the `parentUUID`.
- `ClaimList`: just relay `onClick` and set IDs.
- `RecommendedContent`: now handles the uuid generation (for both parent and child) and stores the data in Redux.
2021-07-28 14:07:49 +02:00
|
|
|
if (claim) {
|
2021-09-03 00:39:40 +02:00
|
|
|
onRecommendationClicked(claim.claim_id, clickedClaim.claim_id);
|
Fill in remaining Recsys fields
## Issue
6366 Recsys Evaluation Telemetry
The recommended list from lighthouse is obtained from `makeSelectRecommendedContentForUri`. This list is further tweaked by the GUI (e.g. move autoplay next item to top, remove blocked content, etc.). Recsys wants the final recommendation list and the clicked index (in exact order), so we need pass these info to the videojs recsys plugin somehow. Also, Recsys wants a recommendation list ID as well as the parent (referrer) ID, we so need to track the clicks and navigation.
## General Approach
- It seems easiest to just spew back the final (displayed) list and all the required info to Redux, and the recsys plugin (or anyone else in the future) can grab it.
- Try to touch few files as possible. The dirty work should all reside in `<RecommendedContent>` only.
## Changes
- `ClaimPreview`: add optional parameters to store an ID of the container that it is in (for this case, it is `ClaimList`) as well as the index within the container.
- When clicked, we store the container ID in the navigation history `state` object.
- For general cases, anyone can check this state from `history.location.state` to know which container referred/navigated to the current page. For the recsys use case, we can use this as the `parentUUID`.
- `ClaimList`: just relay `onClick` and set IDs.
- `RecommendedContent`: now handles the uuid generation (for both parent and child) and stores the data in Redux.
2021-07-28 14:07:49 +02:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2020-08-25 15:49:19 +02:00
|
|
|
return (
|
|
|
|
<Card
|
|
|
|
isBodyList
|
|
|
|
smallTitle={!isMobile && !isMedium}
|
|
|
|
className="file-page__recommended"
|
|
|
|
title={__('Related')}
|
2021-04-08 17:21:45 +02:00
|
|
|
titleActions={
|
|
|
|
signingChannel && (
|
|
|
|
<div className="recommended-content__toggles">
|
|
|
|
<Button
|
|
|
|
className={classnames('button-toggle', {
|
|
|
|
'button-toggle--active': viewMode === VIEW_ALL_RELATED,
|
|
|
|
})}
|
|
|
|
label={__('All')}
|
|
|
|
onClick={() => setViewMode(VIEW_ALL_RELATED)}
|
|
|
|
/>
|
|
|
|
|
2021-04-06 20:59:12 +02:00
|
|
|
<Button
|
2021-04-08 17:21:45 +02:00
|
|
|
className={classnames('button-toggle', {
|
|
|
|
'button-toggle--active': viewMode === VIEW_MORE_FROM,
|
|
|
|
})}
|
2021-04-06 20:59:12 +02:00
|
|
|
label={__('More from %claim_name%', { claim_name: channelName })}
|
2021-04-08 17:21:45 +02:00
|
|
|
onClick={() => setViewMode(VIEW_MORE_FROM)}
|
2021-04-06 20:59:12 +02:00
|
|
|
/>
|
2021-04-08 17:21:45 +02:00
|
|
|
</div>
|
|
|
|
)
|
2021-04-06 20:59:12 +02:00
|
|
|
}
|
|
|
|
body={
|
|
|
|
<div>
|
2021-04-08 17:21:45 +02:00
|
|
|
{viewMode === VIEW_ALL_RELATED && (
|
2021-04-06 20:59:12 +02:00
|
|
|
<ClaimList
|
|
|
|
type="small"
|
|
|
|
loading={isSearching}
|
Fill in remaining Recsys fields
## Issue
6366 Recsys Evaluation Telemetry
The recommended list from lighthouse is obtained from `makeSelectRecommendedContentForUri`. This list is further tweaked by the GUI (e.g. move autoplay next item to top, remove blocked content, etc.). Recsys wants the final recommendation list and the clicked index (in exact order), so we need pass these info to the videojs recsys plugin somehow. Also, Recsys wants a recommendation list ID as well as the parent (referrer) ID, we so need to track the clicks and navigation.
## General Approach
- It seems easiest to just spew back the final (displayed) list and all the required info to Redux, and the recsys plugin (or anyone else in the future) can grab it.
- Try to touch few files as possible. The dirty work should all reside in `<RecommendedContent>` only.
## Changes
- `ClaimPreview`: add optional parameters to store an ID of the container that it is in (for this case, it is `ClaimList`) as well as the index within the container.
- When clicked, we store the container ID in the navigation history `state` object.
- For general cases, anyone can check this state from `history.location.state` to know which container referred/navigated to the current page. For the recsys use case, we can use this as the `parentUUID`.
- `ClaimList`: just relay `onClick` and set IDs.
- `RecommendedContent`: now handles the uuid generation (for both parent and child) and stores the data in Redux.
2021-07-28 14:07:49 +02:00
|
|
|
uris={recommendationUrls}
|
2021-04-06 20:59:12 +02:00
|
|
|
hideMenu={isMobile}
|
2021-06-22 18:33:18 +02:00
|
|
|
injectedItem={SHOW_ADS && IS_WEB && !isAuthenticated && <Ads small type={'video'} />}
|
2021-04-06 20:59:12 +02:00
|
|
|
empty={__('No related content found')}
|
Fill in remaining Recsys fields
## Issue
6366 Recsys Evaluation Telemetry
The recommended list from lighthouse is obtained from `makeSelectRecommendedContentForUri`. This list is further tweaked by the GUI (e.g. move autoplay next item to top, remove blocked content, etc.). Recsys wants the final recommendation list and the clicked index (in exact order), so we need pass these info to the videojs recsys plugin somehow. Also, Recsys wants a recommendation list ID as well as the parent (referrer) ID, we so need to track the clicks and navigation.
## General Approach
- It seems easiest to just spew back the final (displayed) list and all the required info to Redux, and the recsys plugin (or anyone else in the future) can grab it.
- Try to touch few files as possible. The dirty work should all reside in `<RecommendedContent>` only.
## Changes
- `ClaimPreview`: add optional parameters to store an ID of the container that it is in (for this case, it is `ClaimList`) as well as the index within the container.
- When clicked, we store the container ID in the navigation history `state` object.
- For general cases, anyone can check this state from `history.location.state` to know which container referred/navigated to the current page. For the recsys use case, we can use this as the `parentUUID`.
- `ClaimList`: just relay `onClick` and set IDs.
- `RecommendedContent`: now handles the uuid generation (for both parent and child) and stores the data in Redux.
2021-07-28 14:07:49 +02:00
|
|
|
onClick={handleRecommendationClicked}
|
2021-04-06 20:59:12 +02:00
|
|
|
/>
|
|
|
|
)}
|
2021-04-08 17:21:45 +02:00
|
|
|
{viewMode === VIEW_MORE_FROM && signingChannel && (
|
2021-04-06 20:59:12 +02:00
|
|
|
<ClaimListDiscover
|
2021-04-08 17:21:45 +02:00
|
|
|
hideAdvancedFilter
|
2021-04-06 20:59:12 +02:00
|
|
|
tileLayout={false}
|
|
|
|
showHeader={false}
|
|
|
|
type="small"
|
|
|
|
claimType={['stream']}
|
|
|
|
orderBy="new"
|
|
|
|
pageSize={20}
|
|
|
|
infiniteScroll={false}
|
2021-04-08 17:21:45 +02:00
|
|
|
hideFilters
|
2021-04-06 20:59:12 +02:00
|
|
|
channelIds={[signingChannel.claim_id]}
|
|
|
|
loading={isSearching}
|
|
|
|
hideMenu={isMobile}
|
2021-06-22 18:33:18 +02:00
|
|
|
injectedItem={SHOW_ADS && IS_WEB && !isAuthenticated && <Ads small type={'video'} />}
|
2021-04-06 20:59:12 +02:00
|
|
|
empty={__('No related content found')}
|
|
|
|
/>
|
|
|
|
)}
|
|
|
|
</div>
|
2020-08-25 15:49:19 +02:00
|
|
|
}
|
|
|
|
/>
|
|
|
|
);
|
2021-06-28 10:38:48 +02:00
|
|
|
}, areEqual);
|
|
|
|
|
|
|
|
function areEqual(prevProps: Props, nextProps: Props) {
|
|
|
|
const a = prevProps;
|
|
|
|
const b = nextProps;
|
|
|
|
|
|
|
|
if (
|
|
|
|
a.uri !== b.uri ||
|
|
|
|
a.nextRecommendedUri !== b.nextRecommendedUri ||
|
|
|
|
a.isAuthenticated !== b.isAuthenticated ||
|
|
|
|
a.isSearching !== b.isSearching ||
|
|
|
|
a.mature !== b.mature ||
|
2021-09-03 00:39:40 +02:00
|
|
|
(a.recommendedContentUris && !b.recommendedContentUris) ||
|
|
|
|
(!a.recommendedContentUris && b.recommendedContentUris) ||
|
2021-06-28 10:38:48 +02:00
|
|
|
(a.claim && !b.claim) ||
|
|
|
|
(!a.claim && b.claim)
|
|
|
|
) {
|
|
|
|
return false;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (a.claim && b.claim && a.claim.claim_id !== b.claim.claim_id) {
|
|
|
|
return false;
|
|
|
|
}
|
|
|
|
|
2021-09-03 00:39:40 +02:00
|
|
|
if (a.recommendedContentUris && b.recommendedContentUris) {
|
|
|
|
if (a.recommendedContentUris.length !== b.recommendedContentUris.length) {
|
2021-06-28 10:38:48 +02:00
|
|
|
return false;
|
|
|
|
}
|
|
|
|
|
2021-09-03 00:39:40 +02:00
|
|
|
let i = a.recommendedContentUris.length;
|
2021-06-28 10:38:48 +02:00
|
|
|
while (i--) {
|
2021-09-03 00:39:40 +02:00
|
|
|
if (a.recommendedContentUris[i] !== b.recommendedContentUris[i]) {
|
2021-06-28 10:38:48 +02:00
|
|
|
return false;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return true;
|
2018-07-25 02:50:04 +02:00
|
|
|
}
|