f8f9b86cb4
4a22814c broke the intention of if-block (it essentially breaks the functionality in Search page if we enable view counts there in the future).
It also seems completely unrelated to the PR.
48 lines
1.6 KiB
JavaScript
48 lines
1.6 KiB
JavaScript
// @flow
|
|
import React from 'react';
|
|
import 'scss/component/_view_count.scss';
|
|
|
|
type Props = {
|
|
uri: string,
|
|
isLivestream?: boolean,
|
|
// --- select ---
|
|
claim: ?StreamClaim,
|
|
viewCount: string,
|
|
lang: ?string,
|
|
};
|
|
|
|
export default function FileViewCountInline(props: Props) {
|
|
const { isLivestream, claim, viewCount, lang } = props;
|
|
let formattedViewCount;
|
|
|
|
try {
|
|
// SI notation that changes 1234 to 1.2K, look up Intl.NumberFormat() for docs
|
|
formattedViewCount = Number(viewCount).toLocaleString(lang || 'en', {
|
|
compactDisplay: 'short',
|
|
notation: 'compact',
|
|
});
|
|
} catch (err) {
|
|
formattedViewCount = Number(viewCount).toLocaleString();
|
|
}
|
|
|
|
// Limit the view-count visibility to Channel Pages for now. I believe we'll
|
|
// eventually show it everywhere, so this band-aid would be the easiest to
|
|
// clean up (only one place edit/remove).
|
|
const isChannelPage = window.location.pathname.startsWith('/@');
|
|
|
|
// dont show if no view count, if it's a repost, a livestream or isn't a channel page
|
|
if (!viewCount || (claim && claim.repost_url) || isLivestream || !isChannelPage) {
|
|
// (1) Currently, makeSelectViewCountForUri doesn't differentiate between
|
|
// un-fetched view-count vs zero view-count. But since it's probably not
|
|
// ideal to highlight that a view has 0 count, let's just not show anything.
|
|
// (2) No idea how to get the repost source's claim ID from the repost claim,
|
|
// so hiding it for now.
|
|
return null;
|
|
}
|
|
|
|
return (
|
|
<span className="view_count">
|
|
{viewCount !== 1 ? __('%view_count% views', { view_count: formattedViewCount }) : __('1 view')}
|
|
</span>
|
|
);
|
|
}
|